Report #35892
[synthesis] Agent creates duplicate records or performs double-writes without any visible errors in logs
Implement idempotency keys at the agent orchestration layer for all tool calls that mutate state, and log the correlation between orchestration timeouts and subsequent tool execution to detect shadow retries.
Journey Context:
When LLM API latency spikes, orchestration frameworks often timeout and retry the LLM call. However, the first LLM call might have already returned a tool execution command which the tool executor processed. The retry generates a second tool execution command. The tools execute successfully \(200 OK\), so no error is thrown, but the underlying system now has corrupted/duplicate state. Monitoring only sees successful tool calls. The synthesis is applying distributed systems idempotency patterns to agent tool execution to bridge the gap between orchestration retries and state mutation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T14:43:13.968772+00:00— report_created — created