Pending Activations Re-sent Recently
URI: https://docs.ankatech.co/errors/pending-activation-reissue-cooling-down
HTTP Status: 429 Too Many Requests
When you see this
A platform administrator asked to re-send the pending activations of one tenant (reissuePlatformTenantPendingActivations) less than 15 minutes after that tenant's previous re-send. Nothing was read and nothing was issued: every waiting member keeps the link they already had. A tenant is re-sent to at most once every 15 minutes, whoever asks. The bound is counted in a shared store, so it holds across every Admin API instance. Retry-After states how many seconds remain until the tenant can be re-sent to again.
The bound belongs to the tenant, not to the caller. Each re-send mails the tenant's waiting members again and stops their current links working, so two administrators re-sending the same tenant would flood the same people.
A re-send that mailed nothing does not hold the window: a refusal (an unknown or closed tenant, a tenant in PROVISIONING or SUSPENDED, more than 200 members waiting, or the first member's refusal) and a re-send in which every member was skipped leave the tenant available again at once.
Common Causes
- The same tenant was re-sent to twice in a row, for example by two platform administrators at about the same time, or by a repeated click after the first re-send answered.
- A re-send stopped early and was retried at once. The members it did not reach are counted in
notIssued, and they are reached by a re-send once the window ends.
Response Example
{
"type": "https://docs.ankatech.co/errors/pending-activation-reissue-cooling-down",
"title": "Pending Activations Re-sent Recently",
"status": 429,
"detail": "This tenant's waiting members were re-sent their links a short while ago; nothing was issued. Retry after the time the Retry-After header states.",
"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 response carries Retry-After in seconds. The detail is one fixed sentence for every tenant.
How to Resolve
- Wait the number of seconds
Retry-Afterstates, then re-send again if members are still waiting. - To reach one member sooner, the tenant's own administrators re-send that member's link from the tenant's users page (
regenerateActivationToken).
Operations that emit it
| Method | Endpoint |
|---|---|
| POST | /api/v3/admin/platform/users/tenants/{tenantId}/pending-activations/reissue |
Related Errors
- Service Unavailable (503) - the cooldown could not be checked, so nothing was issued; the response carries
Retry-After: 5 - Too Many Pending Activations (409) - more than 200 members of the tenant wait, so nothing was issued
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.