Skip to main content
Every 4xx and 5xx answer is application/problem+json (RFC 9457). The same shape appears inside a job as Job.error. Some codes add members of their own, such as required_scopes or current_etag. Each page shows them in its example. Spend, balance and errors has a handler to copy.

What recommendation asks for

  • fix_request: change the request or its inputs; sent unchanged it fails again
  • wait: work in progress blocks the request; wait for it to end, then retry
  • top_up: the workspace owner adds minutes or changes the plan in the web app
  • retry_later: a temporary failure; retry after a pause (after Retry-After when given)
  • contact_support: Rask has to act; contact support with the instance value

How retry works

  • same_key: resend the same request with the same Idempotency-Key (after Retry-After when given)
  • new_key: start again with a new Idempotency-Key (a failed job)
  • none: do not retry the request unchanged

Every code