Skip to content

Crypto Playground Actor Not Active

URI: https://docs.ankatech.co/errors/crypto-playground-actor-not-active
HTTP Status: 409 Conflict

When you see this

The Cryptographic Playground was asked to run an operation as an Actor that is suspended, disabled or deleted, so nothing ran. The Admin API checks the Actor's status before it requests a token for the Actor, and no token is ever issued for an Actor that is not active. The refusal is recorded as one DENIED admin.cryptoplaygroundexecution.create audit record.

Returned by POST /api/v3/admin/tenants/{tenantId}/crypto-playground/execute (executeCryptoPlaygroundOperation). The cryptographic service applies its own check of the Actor's status too, so a token issued just before a suspension is still refused there.

Common Causes

  • The Actor was suspended.
  • The Actor was disabled, which is permanent, or deleted, after you read the flows.

A suspended Exchange or Internal Crypto Use Case is not this type: a leg its configuration stops is Crypto Playground Combination Not Configured.

Response Example

{
  "type": "https://docs.ankatech.co/errors/crypto-playground-actor-not-active",
  "title": "Crypto Playground Actor Not Active",
  "status": 409,
  "detail": "The Actor is not active, so nothing was run. Reactivate the Actor before running one of its legs.",
  "instance": "/api/v3/admin/tenants/8d2f1c4e-3b7a-4e91-a6d5-0c9f2e8b7a14/crypto-playground/execute",
  "extensions": {
    "requestId": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }
}

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

How to Resolve

  1. Reactivate a suspended Actor, if it was suspended on purpose and should run again.
  2. A disabled or deleted Actor never runs again: configure a new one.
  3. Nothing was run, so running again after the Actor is active cannot repeat an operation.

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