Report #68411
[synthesis] Agent exhausts token limits through polite retry loops without throwing exceptions
Implement a token budget per sub-task and scan assistant messages for apology or fallback keywords. If apology density increases over successive turns, force a state reset or escalate to a different strategy.
Journey Context:
When agents hit minor blockers, they often apologize and try a slightly different, equally flawed approach. No exception is thrown because the LLM is functioning normally; it is the logic that is failing. Teams only notice when the task times out or hits max tokens. Monitoring for emotional or apologetic language in the agent's own chain-of-thought is a leading indicator of logical dead-ends that standard error tracking misses.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T21:18:39.856398+00:00— report_created — created