# Why UpScalp Signals May Not Arrive

**Last reviewed:** 2026-05-22.

Use this page when expected UpScalp messages are missing. The first job is to separate four different situations: no valid setup has appeared, Telegram is not delivering messages, the wrong access path is being checked, or UpScalp has posted a service update.

## First decide what is missing

| What you see                                                         | Most likely area to check first                            |
| -------------------------------------------------------------------- | ---------------------------------------------------------- |
| No recent signals, but official channels are quiet too               | Market conditions or normal signal volume.                 |
| Other Telegram chats notify normally, but UpScalp does not           | UpScalp chat, bot, account, or access path.                |
| No Telegram notifications work                                       | Device or Telegram notification settings.                  |
| Premium messages are missing after a payment or verification attempt | Premium verification and access confirmation.              |
| Several users report the same issue at the same time                 | Status updates and official announcements.                 |
| Approved beta behavior is missing                                    | Approved beta status through the official Access Bot path. |

Do not assume a quiet period is a fault. UpScalp may send fewer messages when market conditions do not produce enough valid setups.

## First check whether Telegram is the problem

1. Confirm Telegram notifications work for another chat.
2. Check device notification permission for Telegram.
3. Turn off Focus mode or Do Not Disturb while testing.
4. Check battery or background-app restrictions.
5. Confirm Telegram is open on the device you actually monitor.

If no Telegram notifications work, fix Telegram/device settings first.

## Then check the UpScalp destination

1. Confirm the chat or bot is listed on [Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links).
2. Confirm the chat is not muted.
3. Confirm the chat is not archived.
4. Confirm you are using the same Telegram account used during setup or verification.
5. Confirm forwarded messages or copied bot links did not lead to a different account, clone, or unofficial group.

Do not troubleshoot from copied links or unofficial search results.

## Check access path

| Expected messages | What to confirm                                                              | Stop point                                                                         |
| ----------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| Lite              | The Lite bot was started from the official link and the chat can notify you. | If the bot was never started or is muted, fix setup before contacting support.     |
| Premium           | Premium verification completed and the same Telegram account is being used.  | If verification is incomplete, use the Premium verification page first.            |
| Private Beta      | Approved beta status exists through the official Access Bot path.            | If beta approval is missing, do not troubleshoot API behavior as a delivery fault. |

If Premium or beta access has not been confirmed, missing messages may be an access issue rather than a delivery issue.

## Check whether this is a service issue

Use [Status and Service Updates](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-status-and-service-updates) when:

1. official announcements mention an incident, delay, maintenance window, or monitoring period;
2. multiple users report the same missing-message pattern at roughly the same time;
3. messages stopped for Lite and Premium at the same time; or
4. support asks users to wait for the next status update.

During a service issue, do not restart setup flows repeatedly or submit the same report several times. Keep timestamps and wait for the next official update unless the status page asks for a specific action.

## When to contact support

Contact support after the checks above point to an account-specific issue or after a status update says the incident is resolved but your messages are still missing.

Send:

1. Telegram username.
2. Product path: Lite, Premium, or approved beta.
3. UTC timestamp when messages stopped.
4. Last UpScalp message received, if there was one.
5. Screenshot or exact error text.
6. Checks already completed from this page.

Do not send private keys, exchange passwords, API secrets, one-time codes, or withdrawal-related credentials.

## Related

1. [Telegram Setup](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-telegram-setup)
2. [Status and Service Updates](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-status-and-service-updates)
3. [Premium Verification](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-premium-verification)
4. [Contact Support](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-contact-support)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-troubleshooting-no-signals.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.