Troubleshooting
Notification problems
Why a digest didn't arrive, why a channel is skipped, and why notifications stay unread until you act.
Last updated June 14, 2026
Most notification questions turn out to be intentional, by-design behaviors rather than bugs — especially around empty digests and read state. Here are the common ones and why they happen.
Troubleshooting
- No digest arrived.
- Check cadence isn't "disabled", and that a channel is enabled. An empty digest (nothing to report) is intentionally not sent.
- Telegram digest skipped.
- The bot token or target chat isn't configured. The channel reports "not configured" and is skipped rather than failing the job.
- Notifications stay unread after a digest.
- By design — sending a digest never marks notifications as read. Mark them read in the notification center.