request.pipe_unspecified
No pipe is selected
| Type | https://mthds.ai/errors/request.pipe_unspecified |
| 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 | 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 request names no pipe_code, and the method gives no main_pipe to start from: its manifest declares none or, with no manifest, its bundles declare none or several.
What to do
Send a pipe_code naming one of params.candidates. The method's author can instead declare a main_pipe, so that a request without pipe_code starts there.
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 | change_input |
Select a pipe with pipe_code, then send the request again. |
| Any other reader | change_input |
Pass this to the caller, who must select a pipe with pipe_code. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
The request selects no pipe, and the method gives no main pipe to start from.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
candidates |
list of identifier |
The pipes the request could select. |
See also
- Executing a method
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry