All error codes

server_unavailable

HTTP 503 Server is temporarily unavailable

What happened

What you asked for could not be read or reached right now. This covers your token, the project behind it, your access to it, whether the API is switched on or, when adding an ISO image, the owner's means to pay not being checkable at the moment, the server record being unreadable, the platform behind it not answering, the server type being disabled, and registries such as backups, images or SSH keys not responding. In object storage it covers the storage not answering or failing within the time of the request, and our records of the storage being unreadable.

What to do

Retry after a short delay. If it was a write request, re-read the resource you were changing first and repeat with a new idempotency key, because the operation may have been submitted before the failure. Only when the detail says nothing was done - for example that the idempotency key cannot be checked right now, or that object storage cannot take the request right now - was nothing started: then the same request can be repeated as it is, with the same key. Attaching or detaching a router on a network is not idempotent, so repeating one of those blindly can answer 409 once it has in fact been applied.

Retrying

The request itself is fine. Repeat it later. After a 5xx to a write request, read the resource first and repeat with a new idempotency key - the operation may have started - unless this page or the detail of the response says nothing was started or changed; then, as after a 409 or a 429, repeat the request as it is.

How it arrives

{
    "type": "https://docs.fiberax.com/errors/server_unavailable",
    "title": "Server is temporarily unavailable",
    "status": 503,
    "code": "server_unavailable",
    "request_id": "a277dcd1ca652c65"
}

Branch your code on code, never on the wording of title.