Skip to content
RelayDocumentation

GuidesCore concepts

Retries

How Relay retries failed deliveries, and how to control it.

A delivery fails when the endpoint returns anything other than a 2xx status, takes longer than 15 seconds, or can't be reached. Relay then retries it with exponential backoff.

Retry schedule

AttemptDelay after the previous one
1Immediately
230 seconds
35 minutes
430 minutes
52 hours
68 hours
7–924 hours

That's nine attempts over roughly three days. Each delay gets up to 10% random jitter so a recovering server isn't hit by every retry at the same time.

Respecting Retry-After

If your endpoint answers 429 or 503 with a Retry-After header, Relay waits that long before the next attempt, up to one hour.

HTTP/1.1 503 Service Unavailable
Retry-After: 120

Which responses are retried

ResponseRetried
2xxNo, delivered
410 GoneNo, and the endpoint is disabled
Other 4xxYes
5xx, timeout, connection errorYes

Respond fast, process later

Return 200 as soon as you have stored the event, then do the work in a background job. Long handlers cause timeouts, and timeouts cause duplicate deliveries.