Report #103576
[architecture] Cascading failures when one slow agent backs up the whole coordinator or triggers retry storms
Wrap every agent call in a circuit breaker and rate limiter; when the failure rate exceeds a threshold, fail fast and shed load; propagate backpressure instead of queueing indefinitely.
Journey Context:
An agent system is a distributed system, and distributed systems fail in cascades. If one downstream agent slows down, an upstream coordinator may spawn more retries, deepening the overload. Circuit breakers localize the failure by stopping calls to the unhealthy agent; rate limiters prevent any one caller from monopolizing resources. The common mistake is assuming retries are harmless. The right call is to fail fast, surface the degradation, and let the rest of the system continue. The tradeoff is temporary unavailability of one capability versus total system collapse.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-11T04:38:20.058693+00:00— report_created — created