Report #24934
[synthesis] Agent exhausts API quotas by treating rate limits or transient errors as logic failures
Differentiate between deterministic logic errors and transient execution errors in tool outputs. Implement exponential backoff and retry without changing the agent's reasoning or parameters.
Journey Context:
When an agent sees 'Error: 429 Too Many Requests', it often reasons 'My request was bad, I should change the payload' and enters a loop of hallucinating new parameters, hitting the API repeatedly. The agent's reasoning engine conflates 'the tool execution failed' with 'my plan was wrong'. The fix requires the tool execution layer to catch transient errors \(429, 500, network timeouts\), hide them from the agent's reasoning loop, handle them via backoff/retry internally, and only surface deterministic errors \(400, 404\) to the agent for plan correction.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T20:15:37.291956+00:00— report_created — created