Skip to content
deedglassdocs

idempotency_key_in_use

An earlier request with the same Idempotency-Key is still running.

HTTP 409 · invalid_request_error · safe to retry

What happened

Section titled “What happened”

An earlier request with the same Idempotency-Key is still running. The response carries Retry-After: 1. Nothing is stored for it.

On POST /v1/actions the Gate waits for the original instead (up to the request’s wait) and answers with the same action. It sends this code only in a rare race: two requests with the same key were admitted at the same moment, and the other one’s action can’t be read yet.

What to do

Section titled “What to do”

Wait a second and retry with the same key. You get the first request’s response once it finishes.

Example

Section titled “Example”
HTTP 409 · idempotency_key_in_use
{
  "error": {
    "type": "invalid_request_error",
    "code": "idempotency_key_in_use",
    "message": "A request with this Idempotency-Key is still running. Retry in a moment.",
    "param": null,
    "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d",
    "doc_url": "https://docs.deedglass.com/errors/idempotency_key_in_use"
  }
}

The message is for a person and can get more exact over time: branch on type and code, never on the message.

In the SDKs

Section titled “In the SDKs”
SDK Raised as
TypeScript (@deedglass/sdk) InvalidRequestError with code === "idempotency_key_in_use"
Python (deedglass) deedglass.InvalidRequestError with .code == "idempotency_key_in_use"
Section titled “Related”