Skip to main content
invalid_run_id means the run_id in the path of a run lookup is not shaped like a run id. Read this page if you read runs back by id, for example to recover a result after a client timeout.

What happened

Routes:
  • GET /v1/runs/{run_id}
  • GET /v1/runs/{run_id}/stream
A run id is run_ followed by a UUID. The value in the path is something else, so OpenType did not look anything up. Both of these forms are accepted: Common causes:
  • The run_ prefix is missing or misspelled.
  • The id was cut short, or carries extra characters such as quotes or whitespace.
  • Another value was used in its place, such as input_digest or the x-request-id.
A well-formed id that does not belong to your organization is a different code: run_not_found. On GET /v1/usage/runs/{run_id} a malformed id gets invalid_parameter instead.

How to fix

Use the run_id exactly as the API returned it, from the POST /v1/runs response, a GET /v1/runs row, or a usage entry. Store it as an opaque string and send it back unchanged.

Example

Reading a run back by the id you stored:
  • Polling - recover a run by id after a client timeout.
  • Conventions - id formats, including the two run id spellings.
  • run_not_found - the id is well formed but not in your organization.
  • Problem codes - every code, its status, and whether a retry can help.