> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get-exo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Timeout

> An operation took longer than its allotted time.

This page is the resolution target of the RFC 9457 `type` URI on every `timeout` problem body: `https://docs.get-exo.com/errors/timeout`.

\*\*HTTP status: `504` \*\*.

```json theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
{
  "type": "https://docs.get-exo.com/errors/timeout",
  "title": "Timeout",
  "status": 504,
  "detail": "The operation timed out.",
  "code": "timeout",
  "requestId": "req_9f2c41ab7d0e5c18"
}
```

## Why it happens

This code exists in the problem envelope's status map. No operation in the published v1 contract declares a 504 response: long work is queued as a job and returns 202 rather than holding a connection open.

The page exists so the `type` URI resolves rather than 404ing if the code is ever emitted.

## How to fix it

* Retry with backoff. If the call had an `Idempotency-Key`, reuse it: the key protects you from a duplicate if the original actually completed.
* For work that is inherently slow, use the async routes and poll the job rather than holding a request open.

## Related

* [`service_degraded`](/errors/service_degraded)
* [`provider_error`](/errors/provider_error)
* [Errors](/platform/errors) for the envelope and the full catalogue