Skip to content

Setup Not Complete

URI: https://docs.ankatech.co/errors/setup-not-complete
HTTP Status: 503 Service Unavailable

When you see this

A business operation that requires a provisioned platform was attempted while first-run setup has not been completed. The readiness gate is fail-closed: a platform in SETUP_REQUIRED, and equally a platform whose readiness cannot be determined, denies the operation rather than letting it fall through to a mutation. Reads, the /platform/setup/* endpoints and actuator health are not gated, so first-run setup and platform-administrator login are never locked out.

Common Causes

  • Creating a tenant before POST /api/v3/admin/platform/setup/complete has been run on a fresh environment.
  • Platform readiness is indeterminate — for example the deployment state row cannot be read — which the gate treats as not provisioned.

Response Example

{
  "type": "https://docs.ankatech.co/errors/setup-not-complete",
  "title": "Setup Not Complete",
  "status": 503,
  "detail": "Platform setup cannot be completed yet.",
  "instance": "/api/v3/admin/tenants",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "8c02fa71-4e3b-4d69-a5f8-30b7c14e9d26"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

  1. Read GET /api/v3/admin/platform/setup/status to see what readiness is missing.
  2. Finish first-run provisioning — declare and bind the key-protection backend — then run POST /api/v3/admin/platform/setup/complete. Completion verifies readiness and only then flips the platform to provisioned; it never half-unlocks.
  3. Retry the original operation once the platform reports provisioned.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.