idempotency_key_reused

This Idempotency-Key was already used for a different request. This Idempotency-Key was already used for a different request in the last 24 hours. Keys identify one request; reusing one for something else is almost always a bug.

• HTTP status: 422 Unprocessable Content
• CLI exit code: 2 (the request or file is not valid)
• Retry: not as it is; the same request will fail the same way until the cause is fixed

How to fix it

Generate a new Idempotency-Key for a new request; reuse a key only to retry the identical request.

What the response looks like

{
  "type": "https://guv.dev/errors/idempotency_key_reused",
  "title": "This Idempotency-Key was already used for a different request",
  "status": 422,
  "code": "idempotency_key_reused",
  "detail": "This `Idempotency-Key` was already used for a different request in the last 24 hours.",
  "fix": "Generate a new Idempotency-Key for a new request; reuse a key only to retry the identical request.",
  "docs_url": "https://guv.dev/errors/idempotency_key_reused",
  "request_id": "req_01jbx2m9k7q4r8t5v6w3y0z1rq"
}

The code field is stable: match on it, not on title or detail, which may be reworded.