TRACE_NOT_FOUND

Cause

The run_id does not resolve to a stored trace. Traces expire on a per-environment TTL (14 days in dev, 90 in staging and production), so an old run reads as missing rather than empty.

How to fix it

Verify the run_id against a recent trace listing; if the run is older than its environment TTL, it is gone.

Example response

{
  "error_code": "TRACE_NOT_FOUND",
  "error_type": "invalid_request",
  "error_message": "No agent-trace run with that run_id.",
  "hint": "Verify the run_id against a recent trace listing; if the run is older than its environment TTL, it is gone.",
  "docs_url": "https://docs.billerapi.com/errors/TRACE_NOT_FOUND",
  "request_id": "d94f5e2a-8c3b-4f1e-9a7d-6b2c1e0f8a34"
}

Related

• Error handling — the error envelope shape and how to parse it
• Error code reference — every stable error code