System transparency
A Telegram alert passes through five separate checks.
A trade must reach an upstream interface, pass Polytrack processing, match an account rule, reach the Telegram Bot API, and arrive in the configured chat. Any stage can add delay or stop delivery.
The delivery chain.
Telegram is the last external handoff, not the start. Polytrack cannot process a trade until an upstream interface makes it available, and it cannot send an account alert until the record has been validated, stored, classified, and matched to that account's settings.
- 1. The trade becomes available upstream.
- 2. Polytrack receives and processes the record.
- 3. The record matches a HIGH severity or watched-wallet rule.
- 4. Telegram accepts the sendMessage request.
- 5. The configured chat receives the message.
The public delay is a separate rule.
The public trade stream deliberately shows records after a 15-minute delay. Account alerts do not use that public presentation rule; they follow the account-delivery path above. They still have no promised end-to-end time.
A valid record can be eligible for one account and ineligible for another because alert switches and watchlists are private account settings. Exact severity thresholds also remain private.
Troubleshoot from the account outward.
First confirm that both the bot token and chat ID are saved and that the relevant alert switch is on. Run the connection test. If setup is correct, check whether the trade qualified for the enabled rule before treating a missing message as a Telegram failure.
A revoked token, invalid chat, blocked bot, network error, rate limit, Telegram outage, or changed setting can stop delivery. A successful API response still does not prove the message was read.
Limits
What this note does not establish.
- Polytrack promises no fixed end-to-end delivery time.
- Market conditions can change before a message arrives or is read.
- Telegram delivery does not execute a trade.