platform-guideline 2 linked patterns checked
Azure Architecture Center: Retry pattern
Documents retry as a transient-failure pattern with immediate, delayed, and cancelled retry strategies based on the failure type and operation.
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 |
|---|---|---|---|
| Offline mobile retry | Choose offline mobile retry when a mobile action should be preserved and retried after connection loss, flaky network, app backgrounding, or policy-limited connectivity. | The UI never reports server success for a mobile action that is only saved locally or queued. | Supports retry strategy selection for transient failures and cancelled retry conditions. |
| 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. | Microsoft documents retry as a transient-failure handling pattern with immediate, delayed, and cancelled strategies. |
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: Microsoft Learn. Last checked: .