Tenant Awaiting Activation

URI: https://docs.ankatech.co/errors/tenant-awaiting-activation
HTTP Status: 409 Conflict

When you see this

An administrator asked for a new link for a pending member of a tenant in PROVISIONING. Nobody can sign in to a tenant in that state, so a link issued now could not be redeemed. No link exists for its members yet: activating the tenant sends every waiting member its own link.

The two operations that answer it are regenerateActivationToken on the tenant plane and regenerateActivationTokenCrossTenant on the platform plane.

Common Causes

• The tenant has not been activated. The member was added, or named as the first administrator, while the tenant was being prepared.
• The request did not come from the console's lists. The pending lists offer no re-send on a row reading AWAITING_TENANT_ACTIVATION, so this answer normally reaches a client calling the operation directly.

A member with nothing to issue is answered 400 before this check:

• On the tenant plane, a membership that is not PENDING.
• On the platform plane, a suspended membership, or an identity that does not have to set a password. A pending member who holds a usable credential therefore answers 400 from the platform plane, and this 409 from the tenant plane. Under a forced password reset the same member answers this 409 from both.

Response Example

{
  "type": "https://docs.ankatech.co/errors/tenant-awaiting-activation",
  "title": "Tenant Awaiting Activation",
  "status": 409,
  "detail": "No link was issued because this tenant has not been activated. Activating it sends the invitation.",
  "instance": "/api/v3/admin/tenants/123e4567-e89b-12d3-a456-426614174000/users/7c9e6679-7425-40de-944b-e07fc1f90ae7/regenerate-activation-token",
  "timestamp": 1765128600,
  "extensions": {
    "requestId": "3f1c2a9e-4b7d-4e2a-9c11-0a2b3c4d5e6f"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. The detail is one fixed sentence for every member of every tenant in this state. Nothing was issued, nothing was mailed and no audit row was written.

How to Resolve

1. Do not retry the request: it is refused for as long as the tenant is in PROVISIONING.
2. Finish preparing the tenant, then activate it with activateTenant. A platform administrator does this from the tenant's detail in the console. See Activating a tenant^*.
3. Every waiting member is mailed its own link by that activation. The re-send is available again afterwards, for a link that expires or never arrives.