Understand notification delivery

An invalidation creates a durable notification delivery record rather than discarding delivery state after an attempt. The current implemented destination is in-app; Payne does not claim email, Slack, Teams, or webhook delivery.

Failed in-app deliveries can be retried with an idempotency key from the gate. Retrying a delivery that is already sent does not create a second notification. The gate preserves attempt count, last error, and sent time so notification failure cannot be mistaken for a successful external alert.

Notification delivery failed

A failed delivery does not reverse the invalidation: the gate remains Previous approval invalidated, but the recorded stakeholder has not received the in-app delivery result.

1. Open the affected gate and inspect the notification status, attempt count, and safe last-error code. This is a read-only check.
2. Confirm the invalidation and required action are still visible before retrying.
3. Choose Retry notification once. Payne reuses the existing delivery record and an idempotency key; it does not create a second invalidation.
4. If retry still fails, preserve the delivery record and report the redacted error code and attempt count. Do not claim an external alert was delivered.

Expected result: the same delivery record shows sent, its error is cleared, and a sent time is present. The underlying gate remains invalidated until its conditions are resolved.