# ERROR_REASONS

<!-- https://uncage.vercel.app/docs/api/client/variables/error_reasons/ -->

```ts
const ERROR_REASONS: object;
```

Defined in: client/src/errors.ts:9

`details.reason` values the client and proxy attach so UIs can tell transport failures apart:
`network` (the request never got a response), `http_status` (a non-JSON error response;
`details.status`), `daemon_unreachable` (the proxy has no token or cannot reach the daemon), `headers` (the
`headers()` option threw).

## Type Declaration

| Name | Type | Default value | Description | Defined in |
| ------ | ------ | ------ | ------ | ------ |
| <a id="property-daemonunreachable"></a> `daemonUnreachable` | `"daemon_unreachable"` | `'daemon_unreachable'` | - | client/src/errors.ts:12 |
| <a id="property-headers"></a> `headers` | `"headers"` | `'headers'` | The `headers()` option threw (e.g. a failed token refresh); code `unauthorized`, status 0. | client/src/errors.ts:14 |
| <a id="property-httpstatus"></a> `httpStatus` | `"http_status"` | `'http_status'` | - | client/src/errors.ts:11 |
| <a id="property-network"></a> `network` | `"network"` | `'network'` | - | client/src/errors.ts:10 |
