Skip to content

Crypto Playground Catalog Too Large

URI: https://docs.ankatech.co/errors/crypto-playground-catalog-too-large
HTTP Status: 422 Unprocessable Content

When you see this

The Cryptographic Playground lists a tenant's flows from the capability grants its Exchanges and Internal Crypto Use Cases hold. One list reads at most 10,000 of them. This tenant holds more readable grants than that, so nothing was listed. A readable grant is a live one, or one used up by its own use limit; a revoked grant does not count, and neither does any grant of another tenant.

Returned by GET /api/v3/admin/tenants/{tenantId}/crypto-playground/flows (listCryptoPlaygroundFlows). The bound is checked by counting before any grant is read. It is one bound for every tenant and cannot be raised for one tenant. The detail names the bound only: it never states how many grants the tenant holds.

Running an operation (executeCryptoPlaygroundOperation) is not bounded this way: a run reads only the grants of the one Exchange or Internal Crypto Use Case it names, for its Actor.

Common Causes

  • The tenant configured more than 10,000 capability grants across its Exchanges and Internal Crypto Use Cases.
  • Automated provisioning created grants that are no longer needed and were never revoked.

Response Example

{
  "type": "https://docs.ankatech.co/errors/crypto-playground-catalog-too-large",
  "title": "Crypto Playground Catalog Too Large",
  "status": 422,
  "detail": "The Cryptographic Playground lists a tenant holding at most 10000 readable capability grants on its Exchanges and Internal Crypto Use Cases, and this tenant holds more, so nothing was listed.",
  "instance": "/api/v3/admin/tenants/8d2f1c4e-3b7a-4e91-a6d5-0c9f2e8b7a14/crypto-playground/flows",
  "extensions": {
    "requestId": "5e2a9c71-0b3d-4f86-a1c4-9d7e2b6f0a38"
  }
}

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

How to Resolve

  1. Revoke the capability grants the tenant no longer uses, on the Exchanges and Internal Crypto Use Cases that hold them. A revoked grant stops counting at once.
  2. Read the flows again once the tenant holds 10,000 readable grants or fewer.
  3. Until then, the console's Playground cannot show this tenant's flows, even when opened from an Exchange or an Internal Crypto Use Case, because it finds them through this list. Operations still run on the Runtime as usual.

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