# cookies_required

> The browser didn't accept the cookie

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

## What it means

Every attempt is tied to the browser with a cookie, and this browser didn't send it back. Nothing has been created. The code is shown on Rivr's error page, and the browser isn't sent back.

## What your system does

Ask the person to allow cookies for Rivr and start over with a new `state` and a new verifier. It can't be solved on your side.

## 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 400 Bad Request
Content-Type: text/html; charset=utf-8
Cache-Control: no-store

<h1>Kopplingen kunde inte startas</h1>
<p>Webbläsaren tog inte emot kakan som kopplingen behöver. Tillåt kakor för den här webbplatsen och starta kopplingen igen från systemet du kom från.</p>
<p>Felkod: cookies_required</p>
```

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