Short answer
Why did a StockNotify Telegram alert not arrive?
If a StockNotify Telegram alert is missing, check the saved alert status first, then check the bot link with /status. Completing setup requires confirming the account link inside Telegram after entering the chat ID in StockNotify. Verify that the intended account is linked, delivery is enabled, and the bot is unblocked.
A price alert's Triggered status records the condition check, not inbox delivery. Use Send test alert to check the current destination. If the problem continues, report the symbol, saved condition, approximate India-time timestamp, and whether the event appeared in the dashboard. Do not share passwords, session tokens, or authentication codes.
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 chat ID, and request a link from StockNotify's authenticated Telegram settings page. Return to Telegram and confirm the account link within 10 minutes. If the request expires, start a fresh one from settings. Refresh the dashboard status and confirm delivery is enabled before sending a test. A chat ID by itself does not establish ownership or complete the connection.
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, and send /start. If the account remains linked, re-enable delivery in settings; if it was unlinked, request and confirm a new link inside Telegram. 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. For a one-time price alert, review the exact symbol, crossing direction, threshold, and Watching or Triggered status. For a trade setup, review the saved entry, stop-loss, target, and lifecycle state. 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.