# order_not_sendable

> The order can't be sent to a device

- Status: 400 Bad Request
- Returned by: /api/public
- Operations: [sendOrderToDevice](https://developers.rivr.io/reference/api-public/sendOrderToDevice.md)
- Retry (`retryWhen`): `never`
- Did anything happen? (`outcome`): `none` (It did not happen)
- Sending an order to a device in /api/public
- Page in the portal: https://developers.rivr.io/errors/order_not_sendable
- Try it: `GET https://developers.rivr.io/errors/simulate/order_not_sendable` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

The order isn't in status `Created`, so it isn't sent to a device. A paid, pending or cancelled order is never sent, since the device starts a payment for what it receives.

## What your system does

Fetch the order and show its status. If the patient is to pay again, a new order with a new id is needed.

## Is it worth retrying?

No, not without changing the call.

`retryWhen`: `never`. Don't send it again. The answer is final for this request: read the current state, the order for example, and act on that.

## 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.

## Example: /api/public

```http
HTTP/1.1 400 Bad Request
Content-Type: application/json

{
  "propertyName": "Status",
  "message": "The order is in status Completed and can therefore not be sent to a device",
  "errorCode": "order_not_sendable",
  "code": "order_not_sendable",
  "type": "https://developers.rivr.io/errors/order_not_sendable"
}
```

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