All error codes

costs_unavailable

HTTP 503 Project costs are temporarily unavailable

What happened

The cost figures for this project could not be read. Your request is correct. On GET /v1/project/costs the billing period could not be resolved, or the metered records could not be loaded. On GET /v1/project/costs/servers the per-server ledger could not be read, or the server records, or the first day of the breakdown, or - without start and end - the billing period. On both, the currency of the amounts could not be determined, or a charge is recorded in a currency with no usable exchange rate. Two other reads never produce this there: a failure of the billing ledger only empties period_total (a charge in it with no usable exchange rate refuses the whole answer, as above), and a failure of the plan catalogue only leaves plan lines named by their key.

What to do

Retry in a few seconds. Nothing in the request needs to change.

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/costs_unavailable",
    "title": "Project costs are temporarily unavailable",
    "status": 503,
    "code": "costs_unavailable",
    "request_id": "a277dcd1ca652c65"
}

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