Protocol
Give retries a budget and one owner
Random delays spread retries; they do not make retry traffic harmless. Bound the work and check which layer is already retrying before adding another loop.
Before you use it
- Use when
- A remote dependency fails transiently and many clients may retry at the same time.
Keep this limit in mind
- Backoff reduces amplification but may increase completion latency; tune it to the service and user-facing deadline.
Current editorial reading
Write a complete retry policy
List recoverable errors, the maximum attempts, an overall time budget, growing delays with random variation, and the action after the budget runs out. Leave room for the caller's deadline. Check SDK and application settings so nested loops do not multiply calls. For a write, verify the API's duplicate-handling contract and preserve the operation identity.
Test the failure path
In a controlled test, make the dependency fail and record actual attempt times and counts. Check that retries spread out, stop at the budget and report a useful failure. Then try a permanent validation or permission error: it should take the defined error path rather than wait through the transient-failure policy. Randomization can still produce coincident attempts; watch total retry load as well as timing.
Take it with you
Count the downstream calls made by one failed user request, including hidden SDK attempts. If that count or total elapsed time exceeds the policy, fix the retry boundary before increasing traffic.
Sources and evidence (1)
What we checked
AWS recommends exponential backoff, randomized intervals, retry limits and testing retry scenarios.
Selected official passages read on 2026-10-04. No fixed attempt count, delay or time budget is claimed to suit every workload.
REL05-BP03 Control and limit retry calls · Implementation guidance; Common anti-patterns
Retries at multiple layers can multiply load, and permanent errors or non-idempotent calls need different handling.
Selected official passages read on 2026-10-04. The impossibility of coincident random retries is not claimed; the proposed test checks a configured policy, not future outage prevention.
REL05-BP03 Control and limit retry calls · Common anti-patterns: multiple layers, error codes and non-idempotent calls
Editorial sources (1)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingGive retries a budget and one owner
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaRetry after a state change; replan after the same failure
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
AWS reliability guidance recommends limiting retries and using exponential backoff with jitter rather than retrying immediately and indefinitely.
Retries are appropriate mainly for transient failures and can worsen overload when used without budgets, timeouts and idempotency.
REL05-BP03 Control and limit retry calls · Implementation guidance
All sources (1)
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details