Task Circuit Breaker
Updated 2026-08-10
INTRODUCTION
English translation pending.
CORE DEFINITION
The Task Circuit Breaker borrows the electrical fuse pattern: when a task or service exceeds a failure or timeout threshold within a window, the system stops attempting it for a period rather than continuing to retry. Its core proposition is that continuing to retry a failing dependency consumes the resources needed elsewhere and propagates the failure outward, so failing fast is the safer behavior. The key qualifier is recovery: the breaker must test cautiously before closing again, and something must serve users in the meantime through a degraded path.
SCAFFOLDING EFFECT
Reduce cognitive load
- Threshold setting: define the failure rate and the time window that will trip the breaker. - Fast failure: stop retrying once tripped instead of consuming resources on a doomed call attempt. - Degraded path: decide in advance what users will get while the breaker is open.
Anchor fast decisions
A failing dependency responds slowly, so each retry holds resources for the full timeout and the backlog grows. When enough callers behave this way, the caller exhausts its own capacity and passes the failure to everything downstream. Stopping attempts early frees the resources, gives the failing component room to recover, and confines the damage to a defined area.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Circuit_breaker_design_patternverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS