Retries making outages worse in .NET services
Service owners add retries to recover, but outage duration increases and queue pressure grows. The hidden issue is usually layered retries, missing stop rules, and no total time budget.
Common symptom variants
Primary playbook
Retry storms don't look like a bug—they look like good engineering until retries amplify failures and multiply in-flight requests during backpressure.
Recommended resource
A decision tree for bounded retries: classify failures, enforce time budgets, and escalate with an operator payload.
Related posts
Polly retries making outages worse: stop retry storms with backoff and jitter
When retries amplify failures instead of fixing them: how retry storms happen in .NET, how to prove it, and the four components that stop cascading failures.
Requests hang forever: why missing timeouts cause recurring outages in .NET
When requests hang forever and recycling releases stuck work: why missing timeouts create backlog, how to add budgets safely, and the rollout plan that prevents new incidents.