Alerts & Notifications

    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.

    Updated 2026-06-15
    2 min read
    inbox
    suppressed
    reasons

    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 keyWhat it means
    Quiet hours activeYour quiet-hours window is currently in effect and the alert is non-critical. Will not be redelivered.
    Queued for digestYour alert frequency is hourly or daily; the alert is batched. Look at the scheduled-for column for the send time.
    Maintenance modeThe site is in an active maintenance window — alerts during planned work are dropped on purpose.
    Duplicate within windowAn identical alert fired recently and was de-duplicated to avoid spam.
    Channel disabledThe destination channel was disabled (e.g. broken webhook, revoked Slack URL).
    Acknowledged elsewhereA 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:

  1. scheduled_for — when the alert *will* be sent if it was deferred (digest only)
  2. mode — hourly or daily, for digest rows
  3. digest — true if grouped into a batch
  4. What to do#

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