Report #16189
[architecture] Two agents bounce a task back and forth indefinitely because neither can resolve the request
Enforce a hard maximum handoff depth limit \(e.g., 5 hops\) and implement a stuck detection mechanism that breaks out to a human or a fallback agent.
Journey Context:
LLMs lack global awareness of the task lifecycle. Agent A thinks Agent B should handle it; Agent B thinks Agent A should. This creates an infinite loop of tool calls. A hard limit on depth is a necessary circuit breaker. The tradeoff is that it might truncate a genuinely complex 6-step pipeline, but infinite loops cost real money and completely break the user experience.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T02:09:19.300736+00:00— report_created — created