run.results_not_stored

The run's results were not stored


Type	`https://mthds.ai/errors/run.results_not_stored`
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 completed and its results were delivered inline in its answer, never stored, so there is nothing to read back.

What to do

Keep the results from the answer that delivered them. A run whose results must be read back later is started the way the runtime stores them, such as with /start.

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	`read_run`	Read the results from the answer the run was started with.
Any other reader	`read_run`	Read the results from the answer the run was started with.

Detail

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

The run '{pipeline_run_id}' completed, and its results were delivered with its answer rather than stored.

Parameters

Every parameter is present on every occurrence of the code.

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