run.failed
The run did not succeed
| Type | https://mthds.ai/errors/run.failed |
| 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 | no: repeating the operation fails the same way |
| HTTP status | 409 |
| Raised as | a problem document, sent as the body of an HTTP response or kept in a run's record |
What it means
A read of a run that ended without success. This problem only says that the run failed; the run's own problem, with its own code and next step, rides run_error.
What to do
Read run_error and act on its code: that problem says who must act and what to do.
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's own problem in run_error to see why it did not succeed. |
| Any other reader | read_run |
Read the run's own problem in run_error to see why it did not succeed. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
The run '
{pipeline_run_id}' ended as '{run_status}', without success.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
pipeline_run_id |
identifier |
The run. |
run_status |
identifier |
The status the run ended with. |
See also
- HTTP Runner Protocol
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry