# clinic_not_ready

> The clinic can't be connected yet

- Status: 302 Found
- Returned by: The account connection (/oauth)
- Retry (`retryWhen`): `later`
- Did anything happen? (`outcome`): `none` (It did not happen)
- The account connection
- Page in the portal: https://developers.rivr.io/errors/clinic_not_ready
- Try it: `GET https://developers.rivr.io/errors/simulate/clinic_not_ready` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

The clinic isn't ready to take payments, or it doesn't have Rivr Plus. The person sees the reason on Rivr's page, but it doesn't come to you. The browser comes back to your address with `?error=clinic_not_ready&state=…`, and nothing is connected.

## What your system does

Check `state` and ask the clinic to finish at Rivr or to contact Rivr. Start over from `GET /oauth/authorize` once the clinic is ready.

## Is it worth retrying?

Only once the situation has changed, see above. Sending the same call straight away gets the same answer.

`retryWhen`: `later`. The same request can succeed, but only once something outside it has changed: another payment has finished, a permission has been given or Rivr has switched something on. Sending it again straight away gets the same answer. Follow the order or wait for the change.

## 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: The account connection (/oauth)

```http
HTTP/1.1 302 Found
Location: https://journal.example.com/rivr/callback?error=clinic_not_ready&state=example-state-from-your-session-32-bytes
Cache-Control: no-store
```

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