Why did a StockNotify Telegram alert not arrive?
If a StockNotify Telegram alert is missing, check whether the price condition was reached, confirm the bot link with /status, verify that the current chat ID is saved and enabled, make sure the bot is not blocked, and check the dashboard event. Then report the symbol, condition, time, and channel without sharing credentials.
Is the Telegram account actually linked?
Send /status in the same conversation that should receive alerts. If it reports no linked account, send /start, copy the new chat ID, and link it again from the authenticated StockNotify Telegram settings page. A chat ID from another account, group, or old conversation will not route messages to the intended destination. The dashboard should show Telegram as linked and enabled before testing delivery.
Has the bot been blocked or disabled?
Telegram returns a permanent error when a user blocks the bot, and StockNotify disables Telegram delivery for that saved destination. Unblock the bot, open the conversation, send /start, and link again if needed. If you intentionally paused or unlinked delivery, restore the enabled setting. Repeatedly saving the same invalid ID will not repair a blocked or different destination.
Did the condition trigger in StockNotify?
Separate condition evaluation from notification delivery. If the dashboard does not show the expected state, review the exact symbol, direction, entry, stop-loss, target, and other saved fields before assuming Telegram failed. Compare timestamps and use the same price source where possible. A broker quote and a third-party feed can differ, especially around gaps, special sessions, or connection interruptions.
Could Telegram or the network be delaying delivery?
Telegram can rate-limit a bot, networks can reset, and the beta service can reconnect after a failure. The backend retries some temporary send errors, but a retry may arrive later and can still fail. Wait long enough to avoid creating duplicate alerts, check the dashboard status, and use email as a secondary record when appropriate. No delivery test or retry policy guarantees every future message.
What details help support investigate a missing alert?
Email service@stocknotify.in with the StockNotify account email, symbol, saved condition, approximate timestamp in India Standard Time, expected Telegram destination, whether the dashboard recorded the event, and a privacy-safe screenshot. Do not include a password, session token, one-time code, or full sensitive account data. Those details let support distinguish a condition issue from a market-data or delivery issue.
How do you prevent notification fatigue?
Keep Telegram for checkpoints that justify immediate review, remove stale conditions, and avoid duplicating the same level across alerts. Use descriptive labels and review the active list each week. A small list makes it easier to notice a real message and easier to identify a failure. Telegram should restore attention; the dashboard, broker, exchange context, and user's own risk process provide the follow-up review.
