method.not_runnable
The method still holds pipe signatures
| Type | https://mthds.ai/errors/method.not_runnable |
| 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 run reached a pipe that is still declared as a signature, with no implementation. Validation reports such pipes as a runnability fact, pending_signatures, rather than as a fault.
What to do
Implement each pipe that pending_signatures lists on the /validate verdict before running the method.
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 |
Implement the signature '{pipe}', then run the method again. |
| Any other reader | contact_owner |
Ask the method's owner to implement the signature '{pipe}'. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
The run reached pipe '
{pipe}', a signature with no implementation.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
pipe |
identifier |
The signature the run reached. |
See also
- Validating a bundle
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry