Report #92252
[synthesis] Agent exhausts context looping on API errors due to stale tool schemas
Implement a 'schema-error' circuit breaker: if a tool returns a validation or client error, do not retry with payload variations; instead, switch to a meta-reasoning step or abort the tool use.
Journey Context:
Agents are trained to 'try harder' when they fail, tweaking payloads to overcome errors. However, you cannot reason your way out of a schema mismatch \(e.g., an API parameter was deprecated\). The agent loops 5 times, trying slight variations of the same fundamentally invalid request. This burns tokens and poisons the context with repeated, unhelpful error messages. Distinguishing between transient server errors \(retryable\) and schema/client errors \(fatal\) is critical to prevent this cascade.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T13:26:15.543411+00:00— report_created — created