Retries and disabling
The retry schedule for failed webhook deliveries, automatic disabling after three days of failures, and manual redelivery.
A delivery succeeds when your endpoint answers 2xx within 10 seconds. Anything else — another status (including redirects), a timeout, a TLS or connection error — is a failed attempt.
Retry schedule
A failed delivery is retried up to 7 times, measured from the first attempt:
| Attempt | After |
|---|---|
| 2 | 1 minute |
| 3 | 5 minutes |
| 4 | 30 minutes |
| 5 | 2 hours |
| 6 | 6 hours |
| 7 | 12 hours |
| 8 | 24 hours |
After the eighth attempt the delivery is marked failed. Every attempt is signed with a fresh timestamp.
Automatic disabling
When every delivery to an endpoint has failed for 3 days in a row, the endpoint is disabled, its pending deliveries are abandoned and your organization's admins get an email. Fix the endpoint and switch it back on under Developers → Webhooks. Endpoints are also disabled when your plan no longer includes webhooks, and re-enabled automatically when it does again.
Delivery log and redelivery
Each endpoint lists its deliveries with the status code, duration and the first 1 KB of your response. Redeliver sends an event again (events are kept for 30 days). Redeliveries are single attempts.
Catching up
If your system was down longer than the retry window, read missed events with the events API (GET /v1/events?created_after=…).
Last updated on