Skip to main content

idempotency-key-not-taken

Status 503, with Retry-After: 30. The type of this problem is the address of this page.

Idempotency-Key is the header's name by default, an API can give it another one, and the detail of the document names the header this API reads.

What happened​

The server keeps every key in a store before the request under it acts, and that store refused to take this one: it took the key on neither of two tries and held no record under it. A store that refuses its writes does that, as a Redis under noeviction does once it has filled up. The request was not carried out, and the refusal reached the error reporting of the API.

What to do​

Send the same request again under the same key once Retry-After has passed. Nothing has acted yet, so the repeat is answered like a first request. An API that answers every write this way needs room in the store that keeps its keys, as Where the keys are kept describes.