> ## 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.

# Not found

> The requested resource does not exist for this caller.

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

**HTTP status: `404` Not Found**.

```json theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
{
  "type": "https://docs.get-exo.com/errors/not_found",
  "title": "Not found",
  "status": 404,
  "detail": "The requested resource does not exist.",
  "code": "not_found",
  "requestId": "req_9f2c41ab7d0e5c18"
}
```

## Why it happens

This is the generic 404 the API falls back to when a route has no more specific code. Most families raise something narrower: `node_not_found`, `job_not_found`, `export_not_found` and so on.

Exo returns 404 rather than 403 for a resource that exists but belongs to someone else. That keeps ids unenumerable: a 403 would confirm the id is real.

## How to fix it

* Confirm the id came from a list route on the same credential.
* If you are addressing another member's resource, that is the expected answer. Resources are scoped to the caller, and a provisioned subject is reached with `X-Exo-Subject` rather than by guessing ids.

## Related

* [`node_not_found`](/errors/node_not_found)
* [`job_not_found`](/errors/job_not_found)
* [`subject_not_found`](/errors/subject_not_found)
* [Errors](/platform/errors) for the envelope and the full catalogue