request.not_found
No such route
| Type | https://mthds.ai/errors/request.not_found |
| Family | request: The HTTP request itself, before any run. |
| 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 route does not exist on this runner. The client was usually written for a newer or an older protocol version than the runner implements, or it called an optional route the runner does not serve.
What to do
Read the runner's GET /version, which reports the protocol version it implements and whether it keeps a blob store, and use a client that matches it, or upgrade the runner.
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 | upgrade |
Use a client written for the protocol version this runner reports in GET /version, or upgrade the runner. |
| Any other reader | upgrade |
Upgrade the client or the runner so that both implement the same protocol version. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
This runner serves no such route.
Parameters
This code declares no parameters, so its problems carry no params.
See also
- The routes
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry