Errors › 409 Conflict

idempotency_request_in_progress

Another request with this `Idempotency-Key` is still running.

What happened

The first request with a key reserves it until it finishes, so concurrent retries can't run it twice. If that request never completes, the reservation lapses after 5 minutes and a retry with the same body runs it.

How to recover

Retry with the same key and body after a short backoff; you'll get the original response once it's stored.

See all errors · API reference