Idempotent Request In Flight

idempotency-key-in-flight · 409

An earlier request with the same Idempotency-Key is still running, so the API won't run the operation twice at once.

That is the protection working, not a failed call.

Besides the members every error carries, this type adds idempotencyKey, endpoint and errors.

Common causes

  • A client timed out on its side and retried while the first request was still running on the server.
  • Two workers picked up the same job and sent it with the same key.

How to fix the call

  • Wait, then retry with the same key. Once the first request finishes, the retry gets its stored response.
  • Don't make a new key to get past this. A new key runs the operation a second time for real.
  • Read endpoint to confirm which operation is running before you decide to wait.

Example response

json
{
  "type": "idempotency-key-in-flight",
  "title": "Idempotent Request In Flight",
  "detail": "A request with Idempotency-Key '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401' is still in flight. Retry shortly to receive the stored response.",
  "idempotencyKey": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "endpoint": "POST /v1/projects/:projectId/services",
  "errors": [
    {
      "field": "Idempotency-Key",
      "message": "an earlier request with this key has not completed yet",
      "value": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401"
    }
  ],
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/services",
  "method": "POST",
  "instance": "POST /v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/services",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/idempotency-key-in-flight"
}