Silences and mutes

None of these change what happens to an event — it still arrives, still opens or updates an incident, and stays fully visible in the inbox and the incident list. They only decide whether a destination is notified about it, and only for alerting reasons: a correction about an incident a destination was already told about is never held back by any of them, so no channel keeps showing an alert that has actually cleared.

There are three, at three different scopes:

	Scope	Set from
Silence	Every source in the workspace, matched by conditions	Notifications → Silences
Mute	One source, everything from it	That source’s own detail page
Snooze	One specific incident	The incident itself, in the inbox

A mute is really a silence narrowed to one source with no conditions — it shows up in the same Silences list, tagged Mute, so you always see everything currently held back in one place.

Silences

Open Notifications → Silences → New silence. Give it:

• Matchers — the same condition fields as a routing rule (minus action, title, body, metadata and time, which are rule-only). Every matcher must hold for a notice to be held back; at least one is required, or it would silence the entire workspace.
• A window — starts now (fixed once created) and either ends at a time you set, or stays open until you end it.

While it’s active, a held-back notice shows in the incident’s timeline as SKIPPED: silenced.

End one early with End now, or delete it outright. The list groups silences into Active now, Scheduled and Expired, and follows the clock while you watch it: one whose window runs out moves to Expired on its own, without a reload. Every time on the page is the workspace’s, named under the heading.

Clearing the Name field of a silence and saving removes the name — the list then shows it as Unnamed silence.

Mutes

From a source’s detail page, Mute it for a set duration or indefinitely. Its events keep arriving and keep opening incidents; only the alerts about them stop. Unmuting it ends the mute immediately — anything it was holding back that’s still open and unacknowledged gets a notice right away, so you’re not left thinking everything’s fine.

Snoozing an incident

From the inbox, snooze one incident until a specific time. It stops alerting until then, and clears any acknowledgement it had. When the time is reached, it returns to open with one notice saying so — snoozing isn’t a way to make something go away, only to defer it. A resolved incident can’t be snoozed.

Next

• Quiet hours — the workspace’s one nightly window, by destination threshold rather than by matcher
• Routing rules — the condition fields a silence’s matchers share with a rule’s when