api concurrency_error ai_generated true

409 Conflict: Idempotency key already used

ID: api/idempotency-key-conflict

Also available as: JSON · Markdown
85%Fix Rate
88%Confidence
3Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
any active — — —

Root Cause

Same idempotency key used for different request body.

generic

Workarounds

  1. 92% success Generate unique idempotency key per unique operation (UUID)
  2. 90% success Reuse key only when retrying the exact same request

Dead Ends

Common approaches that don't work:

  1. Remove idempotency keys 88% fail

    Duplicate charges/operations on retry

  2. Use same key for all requests 80% fail

    All retries return first response