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

# Not found (NOT_FOUND)

> The tool, resource id, or requested time range did not resolve to anything.

## What it means

One of three things happened:

* The tool name in `tools/call` is not registered on this Aeris workspace.
* A resource id in the arguments (campaign id, connection id, org id) does not exist — or is not visible to the caller.
* A range query resolved to zero rows and the tool models empty ranges as a not-found rather than an empty success.

Retrying does not help; the resource has to be created or the identifier corrected.

## How to fix

* List the tool via `tools/list` and confirm the exact tool name and visibility.
* Re-check the id came from the same workspace — cross-workspace ids will look identical but resolve empty.
* For date-range queries, widen the range or verify the connection has data ingested for that period.

## Response envelope

```json theme={"dark"}
{
  "ok": false,
  "error_envelope": {
    "code": "NOT_FOUND",
    "message": "Not found.",
    "docs_url": "https://tryaeris.ai/docs/mcp/errors/not-found",
    "retryable": false,
    "retry_after_ms": null,
    "details": {}
  }
}
```

`details` is empty by default; a handler may add its own keys for context.

## Related

* [`INVALID_INPUT`](/mcp/errors/invalid-input) — the id was malformed, not merely unknown.
* [`CONFLICT`](/mcp/errors/conflict) — the id resolved, but its state does not allow the operation.