Retry policy
Shaded bars: possible range. Dots: 40 simulated clients.
Rate limit: how long will a broadcast take?
Choosing a strategy
- Full jitter spreads clients most evenly and is the usual default for API clients.
- Always prefer the server's Retry-After (or retry_after in Telegram and Discord bodies) when present.
- Only retry idempotent operations automatically, or attach an idempotency key.
- Put a cap on the total time; after that, move the job to a dead-letter queue.
Related: HTTP status codes, Reliability and rate limits guide.