Incidents and delivery history
Check a problem's timeline separately from the delivery of its messages.
On this page
What you need
An alarm rule with an incident or test delivery.
How to do it
- Open the incident to see the condition, its first and latest observation and any recovery.
- Check each destination's delivery state: queued, sent, failed, suppressed or cancelled.
- Acknowledge an incident once you have checked it. This stops reminders but keeps recovery possible.
Good to know
Sent means the notification provider accepted the message, not that you received or read it. Suppressed deliveries show why nothing was sent. Several related alerts may be grouped into one message.
Standard verified accounts share 60 deliveries per hour and 500 per UTC day across all channels. Temporary failures can be retried up to six times. An uncertain provider response can lead to duplicate messages.
If something goes wrong
Acknowledging does not fix the source or change its reading. Check maintenance, mute periods and usage if deliveries are suppressed.
Related guides
- Set up alarms and notifications
Choose meaningful alarm conditions, connect destinations and understand incidents.
- Maintenance, pause and mute
Choose pause, mute or maintenance for planned interruptions.
- Telegram and email setup
Confirm your email destination or connect a private Telegram chat.