# failure.unavailable

Temporarily unavailable: maintenance, missing configuration, overload

Profile: [Errors](https://www.prongs.dev/docs/intents/errors.md) · Raised with: [`fail()`](https://www.prongs.dev/docs/profiles/errors.md) · Status: `503` · Message: generic · Retryable: yes · Writes: [`incident.failed`](https://www.prongs.dev/docs/intents/incident/failed.md)

## Example

```ts
return fail('failure.unavailable', 'SUPABASE_SERVICE_ROLE_KEY is not set.');
```

The caller gets

```bash
HTTP 503

{
  "ok": false,
  "error": "This isn’t available right now. Try again soon.",
  "code": "failure.unavailable"
}
```

And it writes incident.failed

```ts
{
  "intent": "incident.failed",
  "level": "error",
  "alert": true,
  "message": "SUPABASE_SERVICE_ROLE_KEY is not set.",
  "data": {
    "intent": "failure.unavailable"
  },
  "time": "2026-10-09T12:00:00.000Z"
}
```

## Choosing between neighbours

Find the row that describes your case, and use the intent on the right.

| If it is for… | Use |
|---|---|
| Temporarily unavailable: maintenance, missing configuration, overload | `failure.unavailable` (this page) |

## Connections

Declared in the registry, both directions. Where an intent is used in your own code is something check and the gallery see; this site has no app code.

- Built from: [`status.unavailable`](https://www.prongs.dev/docs/intents/errors.md#status-unavailable)
- Writes: [`incident.failed`](https://www.prongs.dev/docs/intents/incident/failed.md)

## For registry authors

**Starter intents.** These are the intents `prongs add errors` puts in your registry, raised with [`fail()`](https://www.prongs.dev/docs/profiles/errors.md). Change the messages to suit your app, and the statuses through the [`status.*`](https://www.prongs.dev/docs/intents/errors.md#status) intents they are built from.

The entry `prongs add errors` writes into your registry. Change the message here, or the status through its [`status.*`](https://www.prongs.dev/docs/intents/errors.md#status) ref.

```ts
'failure.unavailable': {
  kind: 'semantic',
  description: 'Temporarily unavailable: maintenance, missing configuration, overload',
  refs: ['status.unavailable'],
  binding: {
    publicMessage: 'This isn’t available right now. Try again soon.',
    logs: 'incident.failed',
  },
},
```