Troubleshooting and access
Delivery history and retries
Inspect related recipient names, attempts, and delivery IDs without confusing handoff with completed work.
When to use it
Use mailbox history, destination history, and diagnostics to distinguish accepted messages, waiting notifications, and failed delivery.
Example
A webhook times out after the receiver might have accepted its notice. Doorbell may retry the same deliveryId and frozen references. A second destination can succeed independently.
Set it up
- Open Mail for Inbox and Sent, Source message history for acceptance, and Integrations > Destinations for transport attempts.
- An ordinary agent calls mailbox_delivery_status with mailboxId and either messageId or deliveryId. An admin can call get_delivery_history with id set to the trigger's notifierId, or get_destination_diagnostics with the destination's ID as id.
- Inspect delivery identity, activityIds, windowIds, due time, attempts, and outcome. Pending and failed handoffs are not successful ones.
- Repair a failing destination before choosing Retry failed delivery in its website history. Check the original freshness deadline and duplicate-effect risk.
- Correlate canonical message IDs and deliveryId with the receiving workflow to establish what it actually did.
Important limits
- Delivered means HTTP 200 from the webhook, not execution. A timeout can leave acceptance unknown even if the notice arrived.
- Related status rechecks mailbox access on every request. It exposes intended recipient names and states only for that mailbox, without endpoint URLs, keys, raw payloads, or other mailboxes.
- Admin history returns up to 100 deliveries within its seven-day retention, not an unlimited audit log. Counts describe referenced activity, not completed tasks.
- After automatic attempts are exhausted, one eligible manual retry remains before the original deadline. It needs an active trigger on the same destination, that destination's original tested version, and available referenced mail. It keeps the same delivery identity and never makes expired work fresh.
- Manual notification replay is unavailable. Guarded backfill is always silent and adds only eligible existing mail under source access, original expiry, and permanent-removal suppression.
- Pausing or removing a trigger or deleting a mailbox can cancel pending delivery. Removing an agent grant blocks its next mailbox read. Already in-flight requests cannot be recalled.
Troubleshooting
- If work repeats, compare delivery and canonical message IDs, attempts, and separate triggers before retrying.
- If a delivery is too old to retry, arrange any needed work through the authorized workflow. A fresh Inbox check can still find available unread mail; it does not produce a new notice.