# `service_unavailable`

> For the complete documentation index, see [llms.txt](https://www.shortsintel.com/llms.txt). Every docs page is also available as markdown: add .md to its URL. To connect, read [agents.md](https://www.shortsintel.com/agents.md).

The work could not be queued, so the Run failed uncharged.

## Status

HTTP `503`, title `Service unavailable`. One of the [upstream and ours](https://www.shortsintel.com/docs/reference/errors#upstream-and-ours) errors. Branch on `code`, never on the status or the prose.

Retryable: yes. Every body carries this as `retryable: true`, beside `action` and `remedy`: the same request can succeed later, after a backoff or the wait the response names.

## Common causes

- Our background queue did not accept the work.

## What to do

Action: Wait `retry_after_seconds`, then retry; nothing was charged.

We could not start the work right now. The Run failed and nothing was charged; retry with a backoff.

## Example

The body arrives as `application/problem+json`, with `retryable` and the `remedy` above. Most responses add `detail` about the occurrence, and some add fields of their own.

```json
{
  "type": "https://www.shortsintel.com/docs/reference/errors/service_unavailable",
  "title": "Service unavailable",
  "status": 503,
  "code": "service_unavailable",
  "retryable": true,
  "action": "Wait `retry_after_seconds`, then retry; nothing was charged.",
  "retry_after_seconds": 10,
  "remedy": "We could not start the work right now. The Run failed and nothing was charged; retry with a backoff."
}
```

## Related

- [Runs](https://www.shortsintel.com/docs/concepts/runs)
- [Every error code](https://www.shortsintel.com/docs/reference/errors)

[Previous source_unavailable](https://www.shortsintel.com/docs/reference/errors/source_unavailable)[Next internal_error](https://www.shortsintel.com/docs/reference/errors/internal_error)
