Retry schedule
Eight attempts over 36 hours, and what counts as a failure.
3 min read
An attempt succeeds when the endpoint answers with any 2xx status within 15 seconds. Everything else is a failure: a 4xx or 5xx status, a timeout, a refused connection or an invalid certificate.
The schedule
Attempt | Delay after the previous one | Time since the event |
|---|---|---|
1 | Immediately | 0 s |
2 | 30 seconds | 30 s |
3 | 2 minutes | 2.5 min |
4 | 10 minutes | 12.5 min |
5 | 1 hour | 1 h 13 min |
6 | 3 hours | 4 h 13 min |
7 | 8 hours | 12 h 13 min |
8 | 24 hours | 36 h 13 min |
Each delay gets a random jitter of up to 10 percent, so a recovering server is not hit by every retry at the same second.
After the last attempt
The delivery is marked failed and stays in the log, ready to replay. If an endpoint has failed every attempt for 72 hours, Sluice disables it and sends a failure alert.
A 410 Gone response disables the endpoint right away. Customers can use it to unsubscribe from their side.
Something missing or wrong on this page? Tell us at support@sluicehq.dev and we will fix it.