Read The Delivery Ledger
Each ledger entry is one call, newest activity first, with a delivered/total summary such asDelivered 3/3 or Partial 1/3. Expand an entry to see its events in order.
Common Failure Causes
Most failures come from receiver behavior or verification mismatch.Non-2xx response
Timeout
Secret mismatch
URL problem
Retry Behavior
- A failed delivery is retried up to the webhook’s retry count, with a delay between attempts. Retries appear in the ledger with a retry badge and link back to the original attempt.
- Retries re-send the same normalized payload as the original attempt.
- Signatures are computed at send time with the secret as it is then, so a delivery retried after a rotation is signed with the current keys. Verify against any configured key and retries survive rotations.
- Events queued for a webhook that was deleted or deactivated in the meantime are skipped, not delivered and not retried.
Debug A Failed Delivery
1
Open the webhook's Delivery Ledger
Find the call entry; a red summary means at least one attempt failed.
2
Expand the call and read the failed event
The error message and HTTP status tell you whether the receiver, a timeout, or signature verification failed.
3
Download the payload
Replay the exact body against your receiver to reproduce the failure.
4
Fix receiver or secret
Deploy receiver changes or update the configured keys.
5
Trigger a test event
Confirm the next delivery succeeds in the ledger.