Suppressed alerts in the inbox

Why some alerts show as "suppressed" in the Alerts Inbox — quiet hours, digest queueing, maintenance mode — and what each reason means.

Suppressed alerts in the inbox

The Alerts Inbox shows every alert decision — including the ones we chose not to send. A row with status suppressed is an audit trail so you always know why something didn't reach your phone.

Reason labels

Reason key — What it means —

Quiet hours active — Your quiet-hours window is currently in effect and the alert is non-critical. Will not be redelivered. —

Queued for digest — Your alert frequency is hourly or daily; the alert is batched. Look at the scheduled-for column for the send time. —

Maintenance mode — The site is in an active maintenance window — alerts during planned work are dropped on purpose. —

Duplicate within window — An identical alert fired recently and was de-duplicated to avoid spam. —

Channel disabled — The destination channel was disabled (e.g. broken webhook, revoked Slack URL). —

Acknowledged elsewhere — A teammate already acked the parent incident, so this follow-up step was skipped. —

Reading a suppressed row

Each row carries a small context payload with:

• scheduled_for — when the alert will be sent if it was deferred (digest only)
• mode — hourly or daily, for digest rows
• digest — true if grouped into a batch

What to do

• Too many suppressed? Loosen quiet hours or switch from daily to hourly digest.
• Wrong reason? Open the incident — if maintenance mode was on by mistake, end it and re-run the check.
• None at all? That means the engine never even considered the event; see Not receiving alerts.