TickerShare is built so an alert never silently disappears. Every delivery lands in the dashboard log with a status and, when something failed, the reason.
Nothing arrived in Telegram
- Check the delivery log first. If the delivery is there and failed, the reason is next to it.
- Bad token, kicked bot or wrong chat: Telegram rejects fast and the log says so. Re-add the bot in Settings or fix the channel admin rights, then press Retry on the failed row.
- Nothing in the log at all: TradingView never called the webhook. Check the Webhook URL field in the alert and that the alert actually fired.
The card looks wrong
- A field is missing on the card: it was not in the alert message. Blank fields drop off by design. Check the message in TradingView against the format docs.
- The card came as plain text: card rendering failed and delivery degraded to text so the alert still landed. The log shows the delivery as "Text (card failed)". If it repeats, contact us.
Common situations
- Malformed JSON: falls back to the line parser, then to whatever is present. Never an error back to TradingView.
- Telegram flood control (429): the retry_after window is honored and delivery retries after it. Bursts self-heal.
- Over the monthly limit: the alert is HELD in a capped queue, not dropped. Release it or delete it from the dashboard.
- Duplicate alert within 30 seconds: deduplicated to a single delivery.
- Unknown ticker logo: initials badge fallback. The card never renders with a hole.
Retries
Failed deliveries can be retried from the dashboard. A retry re-sends the same delivery in place with no duplicate row and no extra quota count. Automatic retry with backoff also runs on transient Telegram errors and can be toggled per webhook.