Retry Policy
If your endpoint returns a non-2xx status code or a network error occurs, EasyConfirm will retry the delivery.
Retry Schedule
| Attempt | Delay | Total Time Elapsed |
|---|---|---|
| 1st (initial) | Immediate | 0s |
| 2nd (retry) | ~2s | ~2s |
| 3rd (retry) | ~4s | ~6s |
Configuration
| Setting | Value |
|---|---|
| Maximum Attempts | 3 |
| Timeout per Request | 10s |
What Counts as Success
A delivery is considered successful when your endpoint responds with any 2xx status code (200, 201, 202, 204, etc.).
tip
Return 200 OK as quickly as possible. If you need to do heavy processing, acknowledge the webhook first and process the event asynchronously.
What Triggers a Retry
EasyConfirm will retry the delivery if:
- HTTP status code 3xx, 4xx, or 5xx
- Connection timeout (more than 10 seconds)
- DNS resolution failure, connection refused, or any network error
:::caution After All Retries Fail If all 3 attempts fail, the delivery is marked as failed. You can view failed deliveries in the Delivery Logs section of the dashboard. :::