GitHub

failure.unavailable

Temporarily unavailable: maintenance, missing configuration, overload

Profile

Errors

Raised with

fail()

Status

503

Message

generic

Retryable

yes

Writes

incident.failed
View as Markdown

Failure intents

Example

TS
return fail('failure.unavailable', 'SUPABASE_SERVICE_ROLE_KEY is not set.');
The caller gets
Terminal
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

    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.

For registry authors

Starter intents. These are the intents prongs add errors puts in your registry, raised with fail(). Change the messages to suit your app, and the statuses through the 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.* 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',
  },
},