method.pipe_unresolved

The method names a pipe that does not exist


Type	`https://mthds.ai/errors/method.pipe_unresolved`
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

A controller's step, a branch, an outcome or the manifest's main_pipe names a pipe that does not exist.

What to do

Look in params.candidates for the pipe the reference most likely meant, then correct the reference or declare the pipe.

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 pipe '`{missing}`', or correct the reference in pipe '`{pipe}`', then validate the method again.
Any other reader	`contact_owner`	Ask the method's owner to declare or correct the pipe '`{missing}`'.

Detail

The problem's detail is written from this template, filled with the occurrence's parameters:

Pipe '{pipe}' names the pipe '{missing}', which does not exist.

Parameters

Every parameter is present on every occurrence of the code.

Name	Type	Description
`pipe`	`identifier`	The pipe whose declaration names the missing pipe.
`missing`	`identifier`	The pipe reference that names nothing.
`candidates`	list of `identifier`	The pipes the reference most likely meant, the likeliest first.