On Webhooks, the Delivery log is how you debug outbound POSTs.
Before you start
- Open Settings → API & webhooks, then Manage endpoints and the delivery log.
- Scroll to Delivery log.
Read the log
- Use the counts under the heading: delivered · queued · retrying · gave up.
- Optionally pick an event and a status, then press Filter.
- Press Open on a row to see the payload, each attempt, and the HTTP result.
Statuses
- Delivered — your endpoint returned 2xx.
- Queued — waiting to send.
- Retrying — previous attempt failed; another try is scheduled.
- Gave up — attempts exhausted.
The log shows the most recent 100 matching rows. Narrow the filters to see older ones.
Retry schedule
A 2xx is success. Anything else is retried. A 410 Gone stops immediately. Up to 8 attempts, waiting 1 min · 5 min · 15 min · 1 hr · 3 hr · 6 hr · 12 hr between them. After that the delivery gives up. After 5 deliveries in a row give up, the endpoint pauses until you Resume it.
Send again
- Open the delivery.
- Press Send again.
PayBlah queues a new delivery with the same body and the same PayBlah-Event-Id. The original row stays. Deduplicate on that event id. If the endpoint is paused, the flash is “That endpoint is paused. Resume it first, or nothing will be sent.”
Expected result
A healthy endpoint shows Delivered and a last-delivered time. A resend appears as a new row tagged “resend of #N”. A test from the endpoint card appears as test_event.
If something goes wrong
- DNS or TLS failure: Edit the URL, Save changes, then Resume if it auto-paused.
- Auto-pause copy: “Paused automatically after 5 deliveries in a row gave up. Fix the endpoint, then resume it.”
- Resume does not replay events missed while paused.
- Removed endpoint: history remains; you cannot send again to it (“The endpoint it was sent to has been removed.”).
- The payload will not include personal details. Fetch those via the API if your workflow needs them.