Short answers to the questions we hear most, each with the page that goes deeper. If yours is not here, email [email protected].
Almost always because the alert was not routed in. Two things have to be set up: (1) alerts arrive through a source webhook on the Routing page, and (2) an Automation Action with trigger On alert created runs an assistant agent on them. Without (2) you may still see occasional analysis from a legacy link detector, which only catches some alerts. See Routing and Run Assistant Agent. To ask follow-up questions in the thread, tag the bot and start your message with /t.
Yes — use delayed routing in the notification rule. The page is sent after the delay only if the alert is still open and pageable; if it was acknowledged, resolved, or muted in the meantime, nothing is sent. See Routing → Notification rule.
Yes. Choose the HTTP source, send JSON to the webhook URL, and route with a Provider = HTTP condition combined with field or metadata conditions. See Routing.
In the notification rule, add a metadata condition (for example metadata.tag contains /RC) and set the action to Do Nothing. Notification policies and preferences only decide channels and delays; conditional logic lives in Routing.
That is deduplication: alerts with the same dedupKey are merged into the active alert. See Alert Deduplication.
Changes apply to new groups only; existing groups keep the settings they were created with. See Alert Grouping.
Not today. Use Alert Deduplication to merge repeats and Alert mute to pause repeat paging for one alert.
A policy pages only when a Routing notification rule targets it (or the team is paged manually). Also check the person's own setup: phone number in Settings → Profile and channels per priority in Settings → Notifications.