Webhook retry policy
Webhook retry policy
Section titled “Webhook retry policy”Overview
Section titled “Overview”The webhook retry policy automatically retries failed webhook deliveries to ensure your system receives event notifications. When a delivery fails due to a non-2xx status code or a timeout, the system retries the delivery using an exponential backoff schedule. This helps maintain integration reliability during temporary destination server outages.
Prerequisites
Section titled “Prerequisites”None.
- Navigate to Settings → Webhooks.
- Select the webhook that has been marked disabled.
- Re-enable the webhook to reset the retry count and resume deliveries.
- Open the webhook’s delivery log to view the status code and latency for every success and failure attempt (logs are retained for 30 days).
What causes a webhook delivery to fail? A delivery is considered failed if your destination server returns a non-2xx status code or if the delivery attempt times out.
What is the retry schedule for failed webhooks? Failed deliveries are retried with an exponential backoff at the following intervals:
- 1 minute
- 5 minutes
- 30 minutes
- 2 hours
- 12 hours
What happens if all retry attempts fail? After 5 failed attempts, the webhook is automatically marked as disabled, and the system stops attempting further deliveries. You must manually re-enable it to reset the retry count and resume attempts.
Can I configure a custom retry schedule? No. Configurable retry schedules are not supported.