run.answer_not_kept
The run's answer was not kept
| Type | https://mthds.ai/errors/run.answer_not_kept |
| 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 | 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 repeat, under the same idempotency key, of a synchronous run whose first run ended without an answer the runtime kept.
What to do
Read the first run by its id. Sending the request again with a new key would start another 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 | read_run |
Read the run '{pipeline_run_id}' rather than repeat the request. |
| Any other reader | read_run |
Read the run '{pipeline_run_id}' rather than repeat the request. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
The run '
{pipeline_run_id}' under this idempotency key ended as '{run_status}', and its answer was not kept.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
pipeline_run_id |
identifier |
The first run. |
run_status |
identifier |
The status it ended with. |
See also
- HTTP Runner Protocol
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry