Protocols
Saved & recent

Retry backoff and jitter

Also called: exponential backoff, retry jitter, bounded retries

A retry repeats an operation after a failure that may be temporary. Backoff increases the delay between attempts; jitter varies that delay to stop many clients retrying in lockstep. A retry policy also needs limits on attempts or total time and rules identifying which failures are worth retrying.

A hypothetical client could use increasing delay ceilings of 100, 200 and 400 milliseconds, selecting a random wait within each range. These numbers illustrate the pattern rather than recommended defaults. Retrying overload can make it worse, and repeating an operation with side effects requires an idempotent design or another way to determine whether it already succeeded.

Read first
Timeout
Related
Timeout, Idempotency key, Idempotency
Further reading
Amazon Builders’ Library — Timeouts, retries, and backoff with jitter
per-attempt wait windows retry 1 100 ms ceiling 80 ms sample retry 2 200 ms ceiling 47 ms sample retry 3 400 ms ceiling 315 ms sample total budget stops retries hypothetical full jitter
Increasing wait ceilings with randomized delays spread retries. A time or attempt limit stops retries from continuing indefinitely.

View in the full Protocols collection