Skip to content

Request in progress

HTTP 409idempotency_in_progress

When the API answers 409 idempotency_in_progress, and how to fix it.

Version v1.1, updated

The type field of every idempotency_in_progress response links to this page.

On this page

A request with the same idempotency key is still running. BIRP refuses the second one, so the write is not applied twice.

At a glance

  • Status: 409 Conflict

  • Code: idempotency_in_progress

  • Retry: Yes, after a short wait, with the same key.

Causes and fixes

Likely cause

How to fix it

Your code retried before the first attempt ended, often after a short timeout.

Wait a few seconds, then retry with the same key. You get the answer of the first request.

Two workers sent the same job at the same time.

Let one worker own each job, or let the second one wait and retry.

Example

409 idempotency_in_progressJSON
{
  "code": "idempotency_in_progress",
  "detail": "A request with the same Idempotency-Key is still being processed. Retry after it ends.",
  "instance": "/v1/categories",
  "request_id": "a1b2c3d4-0000-4000-8000-0000000000ee",
  "status": 409,
  "title": "Request in progress",
  "type": "https://birp.io/developers/errors/idempotency_in_progress"
}

Related

  • idempotency
  • handling-errors
  • idempotency-key-reused