run.not_found
No such run
| Type | https://mthds.ai/errors/run.not_found |
| Family | run: A run's lifecycle and its reads. |
| Domain | input: the caller acts, by changing the request or its inputs |
| Retry | no: repeating the operation fails the same way |
| HTTP status | 404 |
| Raised as | a problem document, sent as the body of an HTTP response or kept in a run's record |
What it means
The run id names no run this caller can read: it never existed, it belongs to someone else, or its record is no longer kept.
What to do
Check the run id against the one /start or /execute answered with, and the credential against the one that started the run.
Next steps
A problem carries the step aimed at whoever reads it: the first when its reader is the domain's actor, the caller, and the second for any other reader.
| Reader | Kind | Detail |
|---|---|---|
| The domain's actor | change_input |
Check the run id, then read the run again. |
| Any other reader | change_input |
Pass this to the caller, whose run id names no run it can read. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
No run '
{pipeline_run_id}' is visible to this caller.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
pipeline_run_id |
identifier |
The run id the request gives. |
See also
- HTTP Runner Protocol
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry