method.output_concept_mismatch
A pipe's output concept does not fit
| Type | https://mthds.ai/errors/method.output_concept_mismatch |
| Family | method: The method as written, the validation vocabulary included. |
| 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 output concept breaks the rule of the pipe's type or its wiring, such as a PipeLLM declaring an image as its output.
What to do
Declare the output as one of params.expected, or use a pipe type that produces the concept you need.
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 |
Declare the output of pipe '{pipe}' with a concept that fits, then validate the method again. |
| Any other reader | contact_owner |
Ask the method's owner to declare the output of pipe '{pipe}' with a concept that fits. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
Pipe '
{pipe}', a{pipe_type}, declares its output as '{declared}', which does not fit. It accepts:{expected}.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
pipe |
identifier |
The pipe at fault. |
declared |
identifier |
The concept the output is declared as. |
expected |
list of identifier |
The concepts that would fit. |
pipe_type |
identifier |
The pipe's type. |
See also
- Pipes — Operators
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry