Report #92272
[synthesis] Agent becomes overly conservative or hallucinates after multiple retries without crashing
Implement a retry budget that clears the context window or triggers a fresh session with only a summary of the failed attempt, rather than appending raw error traces to the ongoing context.
Journey Context:
Teams monitor for exceptions but miss behavioral degradation. When an agent retries, the error trace stays in context. The LLM attempts to reconcile the failed path with the new path, leading to convoluted logic or extreme risk aversion. Simply increasing max\_retries exacerbates the context pollution. The correct approach is to treat context pollution as a critical failure mode, requiring context isolation or summarization upon error, rather than just blindly retrying.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T13:28:15.771247+00:00— report_created — created