Crypto Playground Delegation Rate Limited

URI: https://docs.ankatech.co/errors/crypto-playground-delegation-rate-limited
HTTP Status: 429 Too Many Requests

When you see this

The Auth API is issuing as many Cryptographic Playground tokens as it allows right now, so it issued none for this run and nothing ran. Its limits are its own: one for each administrator in a tenant, and one for all requests together. Both are distinct from Crypto Playground Rate Limited, the limit on your own executions that the Admin API checks before any token is requested. extensions.failureSource is DELEGATION and extensions.executionStatus is NOT_EXECUTED: the cryptographic service was never called. extensions.runtimeCorrelationId names the execution.

Returned by POST /api/v3/admin/tenants/{tenantId}/crypto-playground/execute (executeCryptoPlaygroundOperation). The response carries Retry-After, a whole number of seconds between 1 and 60: the Admin API relays the Auth API's own delay within that range, and answers 1 when the Auth API gave none it could read. Nothing else of the Auth API's answer is relayed, and the Admin API never retries.

Common Causes

• Many administrators of the deployment are running the Cryptographic Playground at once.
• One administrator runs more executions in a minute than the Auth API admits for one administrator.
• A script runs executions in a loop across several tenants.

Response Example

{
  "type": "https://docs.ankatech.co/errors/crypto-playground-delegation-rate-limited",
  "title": "Crypto Playground Delegation Rate Limited",
  "status": 429,
  "detail": "The authentication service is issuing as many delegated tokens as it allows right now, so the operation was not executed. It is safe to run it again after the Retry-After delay.",
  "instance": "/api/v3/admin/tenants/8d2f1c4e-3b7a-4e91-a6d5-0c9f2e8b7a14/crypto-playground/execute",
  "extensions": {
    "failureSource": "DELEGATION",
    "executionStatus": "NOT_EXECUTED",
    "runtimeCorrelationId": "6f2c1e9a-3d47-4b58-9a10-5e7c2b8d4f36",
    "requestId": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

1. Wait the Retry-After delay and run the operation again: nothing was executed, and no use was spent.
2. If it recurs, ask the operator of the environment whether the Auth API's Cryptographic Playground limits suit the deployment's load. They are listed in Environment Variables — Cryptographic Playground Relay^*.

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