input.invalid
An input does not fit its concept's structure
| Type | https://mthds.ai/errors/input.invalid |
| Family | input: A run's inputs. |
| 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
An input's value fails its concept's structure, such as a required field that is missing or a value of the wrong type, or breaks the rules of its content type. The problem names the field and never what the check found in the value, which a validator's message can quote and which is the content of the run's input.
What to do
Compare the input with its concept's structure at the field params.field names, and correct the value.
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 |
Correct the field '{field}' of the input '{input}', then send the request again. |
| Any other reader | change_input |
Pass this to the caller, who must correct the field '{field}' of the input '{input}'. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
The input '
{input}' does not fit its concept's structure at '{field}'.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
input |
identifier |
The input at fault. |
field |
identifier |
The field of the input that fails, as a dotted path. |
See also
- Concepts
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry