# idempotency_unavailable

> The key could not be checked

- Status: 503 Service Unavailable
- Returned by: /api/public
- Operations: [cancelOrder](https://developers.rivr.io/reference/api-public/cancelOrder.md), [refundOrder](https://developers.rivr.io/reference/api-public/refundOrder.md), [sendOrderToDevice](https://developers.rivr.io/reference/api-public/sendOrderToDevice.md), [createSubscription](https://developers.rivr.io/reference/api-public/createSubscription.md)
- Retry (`retryWhen`): `same_request`
- Did anything happen? (`outcome`): `none` (It did not happen)
- Idempotency-Key in /api/public
- Page in the portal: https://developers.rivr.io/errors/idempotency_unavailable
- Try it: `GET https://developers.rivr.io/errors/simulate/idempotency_unavailable` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

The key could not be checked right now, so nothing was done. On send-to-device and `POST /api/public/subscriptions` the code comes only in the sandbox until the platform's next release; production ignores the header there.

## What your system does

Try again after `Retry-After` with the same key.

## Is it worth retrying?

Yes. The same call can succeed in a while.

`retryWhen`: `same_request`. Send the very same request again, unchanged: the same `Idempotency-Key` and the same order id. Wait `Retry-After` seconds when the answer has the header, otherwise a short while that grows with each attempt.

## Did anything happen?

`outcome`: `none`. **It did not happen.** This call did not do what you asked for and changed nothing else that you can see or that concerns money. Where the code has an `outcomeNote`, it takes precedence.

Nothing concerning the order, the subscription or money. If Rivr also couldn't clean up its half-made claim on the key, the same key can answer `409` `idempotency_in_progress` for up to 24 hours although nothing was done.

## Example: /api/public

```http
HTTP/1.1 503 Service Unavailable
Content-Type: application/json
Retry-After: 5

{
  "propertyName": "Idempotency-Key",
  "message": "The Idempotency-Key could not be checked right now, so nothing was done. Retry the request with the same key.",
  "errorCode": "idempotency_unavailable",
  "code": "idempotency_unavailable",
  "type": "https://developers.rivr.io/errors/idempotency_unavailable"
}
```

The `title`, `detail`, `message` and `error_description` texts are exactly as the API writes them today.