run.lost

The run's outcome is lost


Type	`https://mthds.ai/errors/run.lost`
Family	`run`: A run's lifecycle and its reads.
Domain	`runtime`: nobody could have acted beforehand, so whoever made the call waits, retries or reports the problem
Retry	`outcome_unknown`: the operation may already have taken effect, so its outcome is learned before anything is repeated
HTTP status	`500`
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's execution can no longer be found, or never reported back, so the runtime holds no outcome for it. The run may have done its work, billed calls included, or may still be running, so a new run may repeat that work and is never started automatically.

What to do

Read the run again later, since an execution that has not reported may still end, and check what the run would have produced and the account's usage. Start a new run only once a repeat of the run's work is acceptable. If runs keep being lost, report it to whoever runs the runtime.

Next steps

A problem carries the step aimed at whoever reads it: the first when its reader is the domain's actor, whoever made the call, and the second for any other reader.

Reader	Kind	Detail
The domain's actor	`read_run`	Read the run '`{pipeline_run_id}`' again later in case it reports how it ended, and start a new run only if repeating its work is acceptable.
Any other reader	`read_run`	Read the run '`{pipeline_run_id}`' again later in case it reports how it ended, and start a new run only if repeating its work is acceptable.

Detail

The problem's detail is written from this template, filled with the occurrence's parameters:

The runtime lost track of the run '{pipeline_run_id}', and its outcome is unknown.

Parameters

Every parameter is present on every occurrence of the code.

Name	Type	Description
`pipeline_run_id`	`identifier`	The run.