mobile_rollout_unavailable

HTTP 503§9.1 Transport, authentication, and tenancy

The deployment master is enabled, but the narrow database rollout decision could not be read. The API never assumes a tenant is enabled when that dependency is unavailable.

Problem shape

Every non-2xx response is an RFC 9457 application/problem+json body. The type URI below is stable and machine-matchable, so branch on the final path segment (the code) and treat the status as redundant confirmation. See the error-handling guide.

{
  "type": "https://docs.vocapable.com/errors/mobile_rollout_unavailable",
  "title": "…",
  "status": 503,
  "detail": "…",
  "instance": "/v1/…"
}

← Back to the error registry