Report #65387
[architecture] Agents bouncing a task back and forth indefinitely because neither believes it has the capability to resolve the current state
Implement a maximum handoff depth counter in the message metadata, and a fallback 'catch-all' agent that handles deadlocked tasks.
Journey Context:
Agent A says 'I need DB access, handing to B'. Agent B says 'I need user auth, handing to A'. Loop. Because LLMs are stateless regarding the overall graph traversal, they don't inherently know they are looping. You must track the routing path length. If the handoff count exceeds a threshold, route to a supervisor or generalist to break the cycle.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T16:14:09.489011+00:00— report_created — created