Skip to content

Instance Already Claimed

URI: https://docs.ankatech.co/errors/instance-already-claimed
HTTP Status: 409 Conflict

When you see this

The environment already has its first platform administrator. An environment is claimed exactly once: the claim creates the first platform administrator and closes for good, and no command, host name change or recovery reopens it. Nothing was created.

Only the environment host receives this type: envctl.sh <env> claim-code (POST /api/v3/admin/platform/instance-claim/code, on a host-activation token), which then exits 3 printing instance already claimed and mints no code. A claim start on the console's claim screen is never answered with it: on a claimed instance it is refused instance-claim-code-invalid, like a wrong code, so the public origin never tells whether the instance is claimed.

Common Causes

  • A second operator ran claim-code after the environment was claimed.
  • claim-code was run to recover access to a claimed environment, which it cannot do.

Response Example

{
  "type": "https://docs.ankatech.co/errors/instance-already-claimed",
  "title": "Instance Already Claimed",
  "status": 409,
  "detail": "This instance was already claimed. Sign in with the platform administrator it created; if no administrator can sign in, run recover-platform-access on the environment host.",
  "instance": "/api/v3/admin/platform/instance-claim/code",
  "timestamp": 1792236600,
  "extensions": {
    "requestId": "4b2e8f1a-7c3d-4e9b-a6f0-1d5c8e2b7a93"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. The host command receives this Admin API body, whose correlation identifier is extensions.requestId. See Error Index & Overview.

How to Resolve

  1. Sign in as the platform administrator the claim created.
  2. Give each person who operates the console their own platform identity from Platform Users.
  3. If no platform administrator can sign in, recover one from the environment host with Recover platform access*.

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

* restricted content — see higher-tier documentation