client.timeout
The runtime did not answer in time
| Type | https://mthds.ai/errors/client.timeout |
| Family | client: What a client detects itself, and never receives as a response body. |
| Domain | runtime: nobody could have acted beforehand, so whoever made the call waits, retries or reports the problem |
| Retry | yes: repeating the operation may succeed, after retry_after seconds when the problem gives it |
| HTTP status | none (client) |
| Raised as | an error a client detects itself, never received from a runner |
What it means
A call that creates nothing, such as a read, timed out. A call that may have created a run is client.outcome_unknown instead.
What to do
Try the call again, or raise the client's time limit.
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 | retry |
Try the call again, or raise the client's time limit. |
| Any other reader | retry |
Try the call again. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
The runtime did not answer within
{seconds}seconds.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
seconds |
seconds |
The client's time limit. |
See also
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry