Deliveries
Every notification Capture sends ends up on the Deliveries page of the Notifications app: one row per destination, with its status and outcome. Use it to answer "did that alert mail go out?" without digging through mailboxes and logs.
The list
Each row shows the target, the channel, the (masked) recipient for mail and SMS, the status, how many attempts were made, when it completed, and where the notification came from.
| Status | Meaning |
|---|---|
| Pending | Waiting for its next attempt |
| In flight | Being sent right now |
| Succeeded | Delivered |
| Failed | No more automatic attempts (up to 5 were made) |
When a delivery failed, the row shows a short reason, such as "The receiver answered 503." or "The destination did not respond in time.". The receiver's actual reply, addresses and connection URLs are never shown.
You can filter by target, channel, status, source and time range, and search on the target name or the masked recipient.
The Source column tells you where a delivery came from:
| Source | Meaning |
|---|---|
| Alerting | An alert firing |
| FlowBuilder | A flow's notification block |
| Reporter | An alert-triggered report |
| PlatformApp / Api | An application that sends through the Capture API |
Retry a failed delivery
Open a failed delivery and press Retry. The same delivery goes back in the queue and gets the full retry schedule again. A webhook receiver sees the same delivery id again, so it won't be handled twice by a receiver that deduplicates.
A retry is refused when the delivery is not failed, when its target, channel or connection has been deleted in the meantime, for mail and SMS when the recipient is no longer a member of the channel, within a minute of the previous retry, or after 10 retries of the same delivery.
A retried mail or SMS is sent again and, for SMS, charged again.
Retention
Finished deliveries are kept for 30 days and then removed from the list. Your Capture administrator can change that period. Pending deliveries are never removed.