HTTP 409A request with this idempotency key is still in progress

idempotency_in_progress

A request with this Idempotency-Key is still executing. The ledger refuses to run the same keyed request concurrently — the first request wins; this one should wait and retry.

This page is where the problem type URI https://usepostify.com/docs/api/problems/idempotency-in-progress resolves.

Common causes

  • A client-side timeout fired and the retry raced the original, still-running request.
  • Two workers picked up the same job and sent the same keyed request simultaneously.

How to fix

  • Wait briefly (about a second) and retry with the SAME key — once the original finishes you'll get its recorded response with Idempotency-Replayed: true.
  • Don't switch keys to "unstick" it: a new key risks a duplicate post.

Example response

409 · application/problem+json
{
  "type": "https://usepostify.com/docs/api/problems/idempotency-in-progress",
  "title": "A request with this idempotency key is still in progress",
  "status": 409,
  "code": "idempotency_in_progress",
  "detail": "A request with this Idempotency-Key is currently in progress.",
  "request_id": "req_6f1f8a2b40d34cd2a6f1e2c9b8d7a601"
}

Related