Report #91210
[architecture] Multi-agent workflow loops forever because no agent decides to stop
Designate a termination authority \(a specific agent or a conditional check in the orchestrator\) with explicit halt criteria. Always set a maximum iteration count as a hard backstop.
Journey Context:
This is the halting problem made concrete. Agent A delegates to B, B delegates to C, C has a question and delegates back to A, and the cycle continues indefinitely. Each agent thinks it's being helpful by passing the task along. This is especially pernicious with LLMs because they're biased toward continuing conversation rather than terminating. The fix has two layers: \(1\) a semantic termination condition \(the orchestrator checks if the task output meets acceptance criteria, or a dedicated evaluator agent signals completion\), and \(2\) a hard iteration limit \(max N agent turns\) that forces termination regardless of semantic state. LangGraph implements this via conditional edges that can route to an END node, and via a recursion\_limit parameter on graph execution that halts runaway loops.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T11:41:28.589444+00:00— report_created — created