# clinic_connect_client_refused

> The client may no longer connect

- Status: 409 Conflict
- 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_connect_client_refused
- Try it: `GET https://developers.rivr.io/errors/simulate/clinic_connect_client_refused` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

The sandbox's approval: the client has changed since the request was created and may no longer connect clinics. It may have got a scope outside `public:*` or another platform, or the platform may have got users of its own.

## What your system does

Contact Rivr about how the client is set up.

## 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 409 Conflict
Content-Type: application/json
Cache-Control: no-store

{
  "code": "clinic_connect_client_refused"
}
```

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