run.timed_out
The run passed its time limit
| Type | https://mthds.ai/errors/run.timed_out |
| Family | run: A run's lifecycle and its reads. |
| Domain | method: the method's author acts, by changing the method |
| Retry | no: repeating the operation fails the same way |
| HTTP status | 422 |
| 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 did not end within the deployment's run time limit, so the method's work must shrink to fit it.
What to do
Split the method's work into smaller runs, or have it process fewer items per run.
Next steps
A problem carries the step aimed at whoever reads it: the first when its reader is the domain's actor, the method's author, and the second for any other reader.
| Reader | Kind | Detail |
|---|---|---|
| The domain's actor | change_method |
Make the method do less work per run, so that it ends within {timeout} seconds. |
| Any other reader | contact_owner |
Ask the method's owner to make the method end within the deployment's run limit. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
The run did not end within the deployment's run limit of
{timeout}seconds.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
timeout |
seconds |
The deployment's run limit. |
See also
- HTTP Runner Protocol
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry