Report #1357
[architecture] Hard-coded routing logic sends tasks to the wrong agent when intent is ambiguous, causing infinite handoff loops
Include a confidence score or fallback mechanism in the routing agent's output schema. If confidence is below a threshold, route to a human or a generalist agent, rather than guessing and triggering a ping-pong loop between specialists.
Journey Context:
A common failure mode is the 'ping-pong' effect: Agent A thinks Agent B should handle it, Agent B thinks Agent A should handle it, and they hand off back and forth infinitely. This happens because routing agents are forced to make a discrete choice among specialists. By requiring the router to output a confidence score and defining a threshold for fallback, you break the loop. The tradeoff is an extra LLM call or slightly more complex routing schema, but it prevents runaway token consumption.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-14T19:33:54.228137+00:00— report_created — created