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

# Conversation Not Found

> The referenced agent conversation does not exist or is not accessible to your company.

**HTTP status:** 404

## Error message

```
Resource not found or not accessible.
```

## When this error occurs

`GET /agents/conversations/{id}`, `GET /agents/conversations/{id}/messages`, or
`POST /agents/conversations/{id}/runs` was called with an `{id}` that either:

* does not exist in the system, or
* belongs to a different company than the bearer token's `company_id`.

The response detail is deliberately generic and does not distinguish between the two cases —
the API does not leak existence across company boundaries.

## How to fix

1. Confirm the conversation id is correct (no typos, no truncation).
2. Confirm the token you're using belongs to the company that owns the conversation —
   `GET /whoami` returns your `company_id`.
3. If you recently created the conversation, confirm the `POST /agents/conversations` response
   returned the same `id` you're now passing.

## Variant: a failed run carrying this code

**Surface:** `GET /agents/runs/{id}`, `error.type = "AgentLoopConversationNotFound"`

A run can also fail with this code (rather than a 404) when the agent workflow loads the run's
context and finds the run's conversation row gone. A run always references a conversation, so this
is a data-integrity violation that should not happen in practice — not a caller mistake. It is
non-retryable.

If you see this, report the `log_id` and run id to support; it points at a missing or deleted
`agent_conversations` row for an existing run.