Too Many Pending Activations
URI: https://docs.ankatech.co/errors/pending-activation-reissue-too-large
HTTP Status: 409 Conflict
When you see this
A platform administrator asked to re-send the pending activations of one tenant (reissuePlatformTenantPendingActivations), and more than 200 of that tenant's members are waiting for their activation or invitation link. One re-send mails at most 200 members, and a tenant with more is refused whole: nothing was issued, so every waiting member keeps the link they already had.
The limit applies to the members waiting at the moment of the request, counted the same way the per-tenant pending-activation counts are (listPlatformPendingActivationsByTenant): PENDING memberships of live identities.
Common Causes
- A large tenant onboarded many people at once, and few of them have activated or accepted yet.
- The tenant's invitations were left unattended: every member added and never activated stays pending until they activate, accept or are removed, so the count grows over time.
Response Example
{
"type": "https://docs.ankatech.co/errors/pending-activation-reissue-too-large",
"title": "Too Many Pending Activations",
"status": 409,
"detail": "No link was issued: this tenant has more members waiting than one re-send issues to. Its administrators can re-send each member's link from the tenant's own users page.",
"instance": "/api/v3/admin/platform/users/tenants/123e4567-e89b-12d3-a456-426614174000/pending-activations/reissue",
"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 tenant over the limit; it names neither the tenant's count nor any member.
How to Resolve
- Do not retry the same re-send: it is refused for as long as more than 200 members of the tenant wait.
- The tenant's own administrators re-send each member's link from the tenant's users page (
regenerateActivationToken,POST /api/v3/admin/tenants/{tenantId}/users/{userId}/regenerate-activation-token), or remove the memberships nobody will accept. Once 200 or fewer members wait, the per-tenant re-send is available again. - On a customer-operated deployment (private cloud, on-premises), a platform administrator can also re-send one member's link from the platform plane (
regenerateActivationTokenCrossTenant).
Nothing was changed by the refused request: no link was issued or invalidated, and nothing was mailed.
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.