Alerts or integrations are not delivering

Trace a missing notification from rule evaluation through channel, connection, and on-call routing.

Treat evaluation and delivery as separate stages. A healthy connection does not prove a rule fired, and a firing alert does not prove its destination is configured.

Check the alert state

Confirm the rule is enabled and uses the intended project and environment.
Re-run the query or condition over the same window.
Check threshold, sustained duration, and no-data behavior.
Confirm the alert appears as firing in Alerts.
Check active silences and deduplication before changing the rule.

Use the rule’s test action for configuration validation, but do not treat a test notification as proof that the production condition can fire.

Check the delivery path

Open Settings → Notifications, find the exact routed channel, and choose Test. If it fails:

verify the destination, webhook, email, or routing key;
open Connections and resolve Needs reauth or revoked provider access;
confirm the destination channel or project still exists in the provider; and
check provider-side permissions and delivery logs.

After rotating a secret or reconnecting OAuth, test the saved Teml channel again.

Check on-call routing

Confirm the current schedule has an active responder, the escalation policy references that schedule, and the responder has a valid personal contact method. Overrides and time zones can change who is currently on call.

When escalating to support, include the alert, rule, and channel IDs plus the exact UTC time. Never include provider secrets, API keys, or session cookies.