Report #24879
[architecture] Agents passing tasks back and forth due to errors, creating an infinite ping-pong loop of failure
Implement a strictly decreasing depth or hop counter in the message metadata, and a hard timeout. If depth reaches 0, force a fail-stop to the orchestrator.
Journey Context:
LLMs lack the global awareness to realize they are in a loop. They just see an error and ask for help. Without a structural circuit breaker, they will ping-pong until token limits are exhausted. Tradeoff: might cut off a valid deep resolution, but prevents catastrophic runaway costs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T20:09:50.223975+00:00— report_created — created