platform-guideline 2 linked patterns checked
AWS Builders' Library: Timeouts, retries, and backoff with jitter
Documents retry load risks, capped exponential backoff, jitter, retry limits, and the need to avoid retry amplification during overload.
Read with a purpose
What this source can teach
Use this source to understand a platform convention and the setting it was designed for.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Regenerate / retry | Choose regenerate / retry when the task is rerunning an AI response attempt, creating a new answer version, continuing a failed generation, or recovering from failed AI source or tool work. | Retry same prompt repeats the submitted prompt and visible context unless the UI explicitly shows which context changed. | Supports capped retry, backoff, jitter, and retry-amplification risk for repeated attempts. |
| Retry | Choose retry when a specific failed operation can plausibly succeed if attempted again under the same scope. | Retry repeats the same failed operation against the same request scope unless users explicitly edit that scope first. | AWS documents retry backoff, jitter, retry limits, and how retries can increase load during failures. |
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: Amazon Web Services. Last checked: .