security.schema_refused
An output schema was refused
| Type | https://mthds.ai/errors/security.schema_refused |
| Family | security: Refusals made for safety. An implementation may also record each one as a security event. |
| 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
An output concept's schema carries code-generation extensions or imports that the runtime refuses to execute.
What to do
Describe the concept with the concept structure language alone, without extensions that run code.
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 |
Remove the code-generation extensions and imports from the concept '{concept}', then run the method again. |
| Any other reader | contact_owner |
Ask the method's owner to remove the extensions from the concept '{concept}'. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
The schema of the concept '
{concept}' carries extensions or imports the runtime refuses to execute.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
concept |
identifier |
The concept whose schema was refused. |
See also
- Concepts
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry