Skip to main content

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.

HTTP status: 404

​
When this error occurs

This page covers two distinct sources of the same failure class:
  1. Synchronous — GET /agents/runs/{id} returned 404 because the run id is unknown to the system, or it belongs to a different company. The response detail is generic on purpose; the API doesn’t leak existence across companies.
  2. Asynchronous — error.type = "AgentLoopAgentRunNotFound" on a failed run row means the workflow’s load activity tried to read the agent_runs row by id and got nothing back. This only happens if the row was deleted between API insert and workflow start (unusual; investigate via log_id and the workflow worker logs).

​
How to fix

  1. Verify the run id from the original POST /agents/conversations/{id}/runs response.
  2. Verify your bearer token’s company id matches the conversation that owns the run.
  3. For the workflow-side variant, check the worker logs filtering on the agent_run_<uuid> Temporal workflow id; the load activity logs include the database query result.