Skip to content

How notifications work

An alert reaching you is the last step of a longer chain. Knowing the chain is the fastest way to answer “why didn’t I get told about that?” — the answer is almost always one specific link in it, and History › Notices sent shows exactly which one.

  1. A source sends an event. Proxmox, Uptime Kuma, a script, a heartbeat — whatever it is, it lands as one event with a severity.
  2. Routing rules decide what happens to it. Rules run in order; the first match decides the route: dropped, kept in History, or opened as an incident. An integration’s built-in rules run underneath your own rules, for sources of that integration.
  3. An incident, if one opens, has a notification policy. Who gets told, whether it repeats, whether it escalates if nobody acknowledges — all set on the rule or on Default.
  4. Quiet hours and silences can hold a notice back without touching the incident itself — it still opens, still shows in the inbox, only the alert waits or never goes out.
  5. A destination sends it. Telegram, Slack, Discord, a signed webhook, or the phones paired through InfraInbox Push. A push carries a link back to the incident and each phone’s own unread count for its badge, worked out per phone at send time. A provider that is slow or down delays only its own kind of destination: a Telegram outage never holds up a push to your phone. On InfraInbox Cloud, each workspace also only ever holds its own share of a kind’s sending capacity, so a destination or phone that never answers in another workspace can’t delay yours.
  6. The delivery is recorded either way, sent or not, with why.

Destinations shows each destination as a card: its state (Working, Waiting, Failing), Used by — Default, each rule for some sources and how many other rules send there, each opening the rule it names — its last message and whether it got through, and what quiet hours let through. A failing destination leads with the button that fixes it. The InfraInbox Push card shows how many phones are registered for push and which are yours. Add destination opens a picker of the channels; a destination anything still sends to can’t be deleted until that rule points elsewhere.

Preview routing runs this whole chain against a sample or a past event, live, with nothing sent and nothing stored — the fastest way to check a change before it matters.

Every attempt to tell a destination something — not just the first alert, but every follow-up — is one row in History › Notices sent, including the ones that were held back. Nothing is silently dropped from this list, so it can always answer “who was told, when, and why not.”

Status:

Status Meaning
Pending Queued; shown as “Retrying (n)” once it has already failed once
Processing Being sent right now
Sent The destination’s provider accepted it
Failed Every retry was used up
Cancelled No longer relevant (the incident moved on before it went out)
Skipped Deliberately held back — see below

Why a notice is skipped:

Reason What happened
silenced An active silence or source mute matched the incident
quiet_hours It arrived inside quiet hours, below that destination’s threshold
flapping The incident is unstable; open/resolve notices pause until it settles
cooldown This destination was already told about the incident more recently than its cooldown
destination_broken The destination needs attention (a bad token, a revoked webhook) before anything more is sent
no_edit The channel can’t edit an earlier message, so an acknowledgement, unacknowledgement or snooze made elsewhere has nothing to update there; a resolution still posts a new, silent message (see what “edited in place” means)
edit_failed The message to edit is gone or unchanged, so there was nothing to correct
recovery_off That destination, or that route, has recovery notices turned off
state The notice no longer matches the incident’s current state by the time it was due
drop The rule routed the incident to Drop; recorded only for a later, time-driven notice such as a re-notify
inbox_only The rule routed it to Keep in History; recorded only for a later, time-driven notice
unverified On infrainbox.app only: nothing is sent for a workspace until an owner has confirmed their email address
quota On infrainbox.app only: the workspace, or that one destination, has sent as much as it may today, checked the instant a notice is queued so a burst can’t slip past it — see Usage and limits

A test send — the Send test button on a source or destination — bypasses every one of these gates on purpose: it always goes out, so it always tells you whether the destination itself works.