# clinic_connect_request_not_found

> The request doesn't exist

- Status: 404 Not Found
- Returned by: The account connection (/oauth)
- Retry (`retryWhen`): `after_fix`
- Did anything happen? (`outcome`): `none` (It did not happen)
- The account connection
- Page in the portal: https://developers.rivr.io/errors/clinic_connect_request_not_found
- Try it: `GET https://developers.rivr.io/errors/simulate/clinic_connect_request_not_found` 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: `request` is unknown, has expired after 30 minutes or belongs to another client. All three get the same answer. `POST /api/clinic-connect/requests/{request}/cancel` answers the same way, also when the cookie from `GET /oauth/authorize` is missing.

## What your system does

Get a new request: call `GET /oauth/authorize` with a new `state` and a new verifier, and take `request` from `Location` in the answer. To `cancel`, send the cookie from `Set-Cookie` along.

## Is it worth retrying?

No, not without changing the call.

`retryWhen`: `after_fix`. Change the request first, as the code's page says: a value, the token, a header or a new key. Then send it.

## 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 404 Not Found
Content-Type: application/json
Cache-Control: no-store

{
  "code": "clinic_connect_request_not_found"
}
```

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