Tenant Suspended
URI: https://docs.ankatech.co/errors/tenant-suspended
HTTP Status: 409 Conflict
When you see this
An administrator asked for a new link for a pending member of a tenant that is SUSPENDED. Nobody can sign in to a suspended tenant, so a link issued now could not be redeemed, and it could expire before the tenant is reactivated. Nothing was issued, and the member's outstanding link, if any, is left as it was.
The two operations that answer it are regenerateActivationToken on the tenant plane and regenerateActivationTokenCrossTenant on the platform plane.
Common Causes
- The tenant was suspended after the member was added. The member is waiting for the tenant, and the pending lists read
AWAITING_TENANT_REACTIVATIONfor them. - The request did not come from the console's lists. The pending lists offer no re-send on a row reading
AWAITING_TENANT_REACTIVATION, so this answer normally reaches a client calling the operation directly.
A member with nothing to issue is answered 400 before this check, exactly as for a tenant that has not been activated (see Tenant Awaiting Activation).
Response Example
{
"type": "https://docs.ankatech.co/errors/tenant-suspended",
"title": "Tenant Suspended",
"status": 409,
"detail": "No link was issued because this tenant is suspended. Reactivating it sends the invitation to everyone still waiting.",
"instance": "/api/v3/admin/platform/users/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 suspended tenant. Nothing was issued, nothing was mailed and no audit row was written.
How to Resolve
- Do not retry the request: it is refused for as long as the tenant is
SUSPENDED. - Reactivate the tenant with
reactivateTenantwhen the reason for the suspension is resolved. A platform administrator does this from the tenant's detail in the console. See Tenant Lifecycle States*. - The reactivation mails a link to every member still waiting: anyone added during the suspension, and anyone whose link expired during it. A member whose link is still valid keeps it. The re-send is available again afterwards, for a link that expires or never arrives.