Unprocessable entity
The request was well formed, but it asks for something that is not allowed as things stand. The answer's detail says why.
What this means
The values are valid one by one, but together, or with the current state of the resource, they break a rule. For example a setting that needs another setting to be on first.
How to fix it
Read the detail in the answer. Change the request, or make the change it names first, then send the request again.
Retry behavior
Sending the same request again gets the same answer until the request or the resource changes.
How it appears in the response
ComputeSphere returns errors as RFC 7807 Problem Details. The type field is the docs URL for this page — switch on code in your client.
{
"type": "https://docs.computesphere.com/errors/unprocessable_entity",
"title": "Unprocessable entity",
"status": 422,
"code": "unprocessable_entity",
"detail": "The request was well formed, but it asks for something that is not allowed as things stand. The answer's detail says why.",
"instance": "/v2/…",
"request_id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
"trace_id": null
}
The Content-Type header is application/problem+json. On field-level validation errors a non-empty errors[] array also appears, each entry carrying its own docs_url for the offending field.