Bad gateway
A service that ComputeSphere depends on to answer this request did not answer correctly.
What this means
A fault in a system behind the API, on our side or at a provider you connected (for example your Git provider). The answer's detail says what could not be done.
How to fix it
Try again in a moment. If it keeps happening, contact support and include the request_id from the answer.
Retry behavior
Safe to retry a read after a short wait. For a change, check whether it was applied before sending it again.
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/bad_gateway",
"title": "Bad gateway",
"status": 502,
"code": "bad_gateway",
"detail": "A service that ComputeSphere depends on to answer this request did not answer correctly.",
"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.