# temporarily_unavailable

> The connection can't be started at the moment

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

## What it means

The account connection isn't switched on for your platform at the moment. Rivr switches it on per platform, and it is off until Rivr has done so. The same answer comes when Rivr is getting too many new attempts at once, for all platforms together or from the same address. The browser comes back to your address with `?error=temporarily_unavailable&state=…`. The sandbox's approval answers `503` with `{"code":"temporarily_unavailable"}`. Disconnecting always works.

## What your system does

Check `state`, show that the connection can't be made at the moment and let the person try later, with a new `state` and a new verifier. Contact Rivr if the connection should be on for your platform.

## 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=temporarily_unavailable&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.