Report #72404
[synthesis] Agent enters infinite retry loop or abandons tool use after a single tool execution error
After a tool error, inject model-specific recovery guidance in the tool result message: for GPT-4o, append 'Do not retry the same call with identical parameters. Modify your approach based on this error.'; for Claude, provide the full error output and it will typically self-correct; for Gemini, explicitly restate the available tools and ask it to try an alternative. Always include structured error details \(not just 'error occurred'\) in tool results.
Journey Context:
Error recovery is where model behavioral fingerprints diverge most sharply in agentic loops. Claude tends to read error output, diagnose, and adjust its approach—often switching tools or parameters. GPT-4o has a documented tendency to retry the identical failing call, especially if the error message is vague. Gemini may abandon tool use entirely and fall back to free-text speculation. These are not random—they reflect different training data distributions around error recovery patterns. The synthesis: your error-handling code must be model-aware, because each model has a characteristic retry pathology that a generic retry counter cannot fix.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T04:06:57.151077+00:00— report_created — created