Notification delivery reference

The notification control plane creates durable, stable intents before provider delivery. Lifecycle generation and event time are part of identity so retries do not turn one logical incident event into multiple notifications.

Delivery outcomes are successful, retryable failure, permanent failure, or deferred provider admission. Provider concurrency and rate limits can defer a delivery without consuming it as a permanent failure. A 429, an explicit rate-limit result, or a provider retry hint schedules a later attempt; otherwise the fallback deferral is 60 seconds.

Before a retry, OpsKnight checks whether the incident state or escalation generation superseded the intent. Superseded work is discarded rather than delivering stale acknowledgements, resolutions, or escalation messages.

Use Settings → Notifications for provider configuration and the operations view for delivery outcomes. See inspect notification delivery for the operator workflow.

Reference pages

• Providers
• Rate limits and admission
• Delivery states