run.outcome_unknown

The runtime cannot tell whether the run started or finished


Type	`https://mthds.ai/errors/run.outcome_unknown`
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	`502`
Raised as	a problem document, sent as the body of an HTTP response or kept in a run's record

What it means

The runtime sent the run on to be executed and lost the answer, so the run may have started, may have finished, or may never have begun.

What to do

Read the run by its id to learn its outcome. A repeat of the request may start a second run, so it is never made automatically.

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}`' to learn its outcome, and never send the request again automatically.
Any other reader	`read_run`	Read the run '`{pipeline_run_id}`' to learn its outcome, and never send the request again automatically.

Detail

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

The run '{pipeline_run_id}' was sent on, and its answer was lost.

Parameters

Every parameter is present on every occurrence of the code.

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