idempotency_in_progress
HTTP 409 A request with this Idempotency-Key is still running
What happened
An earlier request carrying this `Idempotency-Key` is still running, so this one was not executed at all. A key holds one logical operation at a time. This answer is for an exact repeat of the running request: one that differs from it (method, path, body, query parameters, caller) is refused with idempotency_key_reused (422) even while the first is still running. Two requests sent with an unused key at the same instant are the exception - the later one gets this answer whatever it carries.
What to do
Wait for the interval in the Retry-After header, then send exactly the same request with the same key. If the first request finished successfully you get its stored response; if it ended in a conflict, a payment refusal or a platform error nothing was stored, and your request runs for real. An abandoned in-flight record is released after two minutes.
Retrying
The request itself is fine. Repeat it later. After a 5xx to a write request, read the resource first and repeat with a new idempotency key - the operation may have started - unless this page or the detail of the response says nothing was started or changed; then, as after a 409 or a 429, repeat the request as it is.
How it arrives
{
"type": "https://docs.fiberax.com/errors/idempotency_in_progress",
"title": "A request with this Idempotency-Key is still running",
"status": 409,
"code": "idempotency_in_progress",
"request_id": "a277dcd1ca652c65"
}
Branch your code on code, never on the wording of title.