Go to App
resilience/rate-limit-backoffs

Rate Limit Backoffs

How 429 and quota responses delay one channel without pausing the fleet.

Strategy

When a marketplace returns 429 or a quota error, **that bulkhead** waits. Other channels do not inherit the delay.

We prefer the server’s instructions over a guessed sleep.

Retry-After

If the response includes Retry-After (seconds or HTTP date), the job waits at least that long. Ignoring Retry-After is how you get longer bans.

Jitter

Exponential backoff is jittered so 50 jobs do not retry on the same millisecond. Full jitter (or equal jitter) avoids thundering herds when a quota window resets.

Telemetry

Latency, status class, and error codes are recorded for admin dashboards and the SSE traffic stream. Use them to see “Amazon 429 for 10 minutes” vs “our transformer 400.” Those are different fixes.