Transient failure
A transient failure is a temporary failure condition that may resolve on its own or not recur when an operation is attempted again.
ASP.NET Core in Action, 3e
A transient error is a temporary failure, such as a network or service interruption, that may succeed when the operation is retried.
- How it is used
- Handles temporary failures when applications call remote HTTP APIs.
- How deep it goes
- Explains causes, handler-pipeline placement, retry configuration, policy choices, and safety trade-offs without detailing Polly internals.
- Examples
- Uses remote API outages, network drops, timeouts, 5xx responses, and a typed exchange-rates client with three retry delays.
- What you can do after
- Configure automatic retries for transient HTTP failures through a named or typed HttpClient.
Read how ASP.NET Core in Action, 3e explains transient failure →
Think Distributed Systems
A failure whose subsequent occurrence probability is not elevated and that resolves automatically without intervention.
- How it is used
- Classifies failures by recurrence probability and automatic repair within a distributed-system failure model.
- How deep it goes
- Defines conditional-probability and autorepair criteria, then contrasts intermittent and permanent failures without detailing detection mechanisms.
- Examples
- Uses a restarting router, a briefly absent employee, and recovered executions that may duplicate prior events.
- What you can do after
- Evaluate failure classifications and reason about whether recovery can preserve an execution’s application-defined outcome.
Read how Think Distributed Systems explains transient failure →
Related concepts
- retryaddressed by · A retry is a subsequent attempt to perform an operation after an earlier attempt fails or does not complete successfully.
- exponential backoffaddresses · Exponential backoff is a retry strategy that progressively increases the delay between successive attempts after failures, typically by a multiplicative factor.
- Pollyaddressed by · Polly is a .NET resilience library for defining policies that handle transient faults and control behaviors such as retries, timeouts, circuit breakers, and fallbacks.
- application-level failurecontrasts with · An application-level failure is an inability of software to perform its intended operation because of application logic, defects, invalid inputs, or unmet application conditions.
- stale dataaddressed by · Stale data is information that no longer reflects the current state of its underlying source or relevant conditions.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.