Report #78848
[agent\_craft] Agent repeatedly calls failing tool with identical arguments
Implement exponential backoff with argument mutation: after first failure, retry with same args; second failure, retry with simplified args \(reduce parameters by 50%\); third failure, escalate to user; never retry >3 times. Parse error types: 4xx client errors \(don't retry\), 5xx server errors \(retry\), execution errors \(mutate\).
Journey Context:
Common antipattern is infinite retry loops on deterministic errors \(e.g., file not found\). Tradeoff: some failures are transient \(network\) vs permanent \(file deleted\). Alternatives: 'immediate user escalation' interrupts flow for transient issues; 'automatic arg mutation' risks changing intent. Specific rule: parse error type - 4xx client errors \(don't retry\), 5xx server errors \(retry\), tool execution errors \(mutate args\). Maintain error counter in conversation state. Critical: distinguish between 'tool not found' \(permanent\) and 'tool timeout' \(transient\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T14:56:11.355496+00:00— report_created — created