Delivery and retries
What counts as delivered, when Pepvote retries, and when it gives up.
A delivery succeeds when your receiver returns any 2xx within 15 seconds. Redirects are not followed, so point the endpoint at the final URL. Return the 2xx only after you have accepted the event.
Retry schedule
Anything other than a 2xx (error status, timeout, network error, redirect) is retried up to five more times:
| Attempt | Sent |
|---|---|
| 1 | Immediately |
| 2 | 1 minute later |
| 3 | 5 minutes later |
| 4 | 30 minutes later |
| 5 | 2 hours later |
| 6 | 8 hours later |
Retries reuse the same event ID and body. Treat the event ID as an idempotency key.
Auto-disable
Each failed attempt adds to the endpoint's consecutive failure count; a success resets it. After 15 consecutive failures, Pepvote disables the endpoint. Fix your receiver, then select Enable. Missed deliveries are not replayed.
Delivery log
Open the endpoint and look at Webhook deliveries. Each attempt shows the event ID and type, attempt number, time, duration, request body, response body (up to 4 KB), and any network error. Filter by status, response group, event type, or event ID. Records are kept for at least 30 days.
| Status | Meaning |
|---|---|
| Pending | Queued |
| Succeeded | Got a 2xx |
| Failed | The final attempt did not succeed |
Related help
Last updated September 4, 2026