# unavailable

> The unavailable Problem Details code: A dependency is briefly unavailable.

Source: https://docs.nexafone.so/v1/errors/unavailable/

| | |
| --- | --- |
| HTTP status | `503` |
| Area | General |
| Problem `type` | `https://docs.nexafone.so/errors/unavailable` |

A dependency is briefly unavailable. Retry with exponential backoff.

## What the `detail` says

The `detail` explains the occurrence; it can read, for example:

- Billing lists across workspaces are not configured.
- Connecting WhatsApp is not available on this server yet. Try again later.
- Embeds are unavailable right now. Try again shortly.
- File storage is not configured.
- Idempotent requests cannot be accepted right now. Try again later.
- Meta webhooks are not configured on this server.

## Handling it

Briefly unavailable; retry with backoff.

## Example

```json
{
  "type": "https://docs.nexafone.so/errors/unavailable",
  "title": "Service Unavailable",
  "status": 503,
  "code": "unavailable",
  "detail": "Billing lists across workspaces are not configured.",
  "requestId": "01J9Z8Q4TQ3W6M5V2X7Y8Z9A0B"
}
```

Match on `code`, never on `detail`: the wording may change. See [Problem Details](/v1/errors/).