Retry Policy
Retry Policy
Webhooks will now be retried a total of 6 times over 12 hours using an exponential backoff schedule. This should allow sufficient time for transient errors to be resolved.
The retry policy is designed to handle temporary issues that may prevent the webhook from being delivered successfully. This includes network issues, server downtime, or other transient errors.
| Attempt | Waiting time (approx.) | Total cumulative time |
|---|---|---|
| 1 | 1 min (60s) | 1 min |
| 2 | 4 min (252s) | 5 min |
| 3 | 16 min (1061s) | 21 min |
| 4 | 1 h (4457s) | 1h 25min |
| 5 | 4 h (18723s) | 5h 41min |
| 6 | 12 h (43200s) | 17h 41min |
If the webhook fails to deliver after the last attempt, it will be marked as failed and no further retries will be attempted. You can check the status of your webhooks in the admin panel.
You can check the status of your webhooks and reprocess it (if needed) manually from the admin panel.
Updating the subscription's address during a retry cycle will not result in the webhook being delivered to the new address.
Updated 9 months ago