request.pipe_ambiguous

The pipe selection matches several pipes


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

A bare pipe code matches pipes in several domains or methods, so the runtime cannot tell which one the request means.

What to do

Pick one of params.candidates and select it by a reference that names it alone, such as its domain-qualified reference.

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 one of the matching pipes by a reference that names it alone, then send the request again.
Any other reader	`change_input`	Pass this to the caller, who must select one of the matching pipes unambiguously.

Detail

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

The pipe selection '{pipe}' matches several pipes: {candidates}.

Parameters

Every parameter is present on every occurrence of the code.

Name	Type	Description
`pipe`	`identifier`	The pipe selection the request gives.
`candidates`	list of `identifier`	The pipes the selection matches.