Report #98543
[synthesis] Agent retries a non-idempotent operation after a transient failure, duplicating or corrupting state
Make every mutating tool idempotent \(use idempotency keys, upserts, or conditional writes\) and distinguish retryable from non-retryable errors.
Journey Context:
Retries are the default recovery strategy, but not all operations can be safely repeated. A failed 'create user' may have partially succeeded; retrying creates a duplicate. The synthesis combines HTTP semantics \(POST is not idempotent\) with agent behavior \(blind retry loops\). The fix is to design operations so the second identical call has no additional effect.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-27T05:09:08.367805+00:00— report_created — created