Skip to main content

What this error means

SERVICE_UNAVAILABLE is returned with HTTP status 503 when a dependency the request needs is temporarily unavailable: a brief database connectivity blip, load shedding while the platform protects core paths under heavy load, or a required database object that is not ready yet for your organization. The request was not processed; retrying after a short pause is expected and safe. Every response for this error carries this page’s address in meta.docs_url:

Cause

How to fix it

  1. Retry with backoff. This is a transient fault: wait a second or two and reissue the request, doubling the wait between attempts. Honor a Retry-After header when one is present.
  2. Do not retry at full speed. An immediate retry loop converts one shedding event into a self-inflicted rate-limit problem on top of it.
  3. Check the status page for sustained windows. If 503s continue for more than a few minutes, status.orbit.devotel.io shows whether the platform is in a declared incident.
  4. Include meta.request_id if you open a ticket. It lets support pull the exact request from logs.