Before you use it
- Use when
- A dependency is persistently failing or timing out and retries add more load without useful progress.
Keep this limit in mind
- Circuit breakers can block a recovered service if thresholds or probe logic are poor; tune and monitor them.
Why it matters
Track recent dependency failures. When failure crosses the defined threshold, stop normal calls temporarily and fail or degrade locally. After a recovery interval, allow a small number of probe calls before reopening normal traffic. Make breaker state visible to operators.
Steps
- Failure threshold is defined.
- Open state stops normal calls.
- A fallback or explicit failure path exists.
- Half-open probes are limited.
- Successful probes close the circuit.
- Breaker state and transitions are observable.
An example
An agent stops calling a failing external search service after repeated timeouts and periodically tests recovery with one low-rate request.
Check your result
A persistently failing dependency cannot trigger unlimited retries from every caller.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
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 readingOpen the circuit when a dependency keeps failing
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaFail work that cannot meet its useful deadline
Evidence and sources
Circuit breakers stop repeatedly failing calls to an unhealthy dependency and later allow limited probes to detect recovery.
Poor thresholds can open unnecessarily or delay recovery; breaker state needs observability.
Circuit breaker pattern · Intent and open/half-open/closed states
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.


