Skip to content

Crypto Playground Execution Status Unknown

URI: https://docs.ankatech.co/errors/crypto-playground-execution-status-unknown
HTTP Status: 504 Gateway Timeout

When you see this

A Cryptographic Playground operation was sent to the cryptographic service and no usable answer came back: the deadline passed (20 seconds by default), the connection was lost after the request was written, or the answer was larger than the deployment's response limit. The operation may have run. extensions.executionStatus says so with UNKNOWN, and extensions.runtimeCorrelationId names the execution.

Returned by POST /api/v3/admin/tenants/{tenantId}/crypto-playground/execute (executeCryptoPlaygroundOperation). The identifier in extensions.runtimeCorrelationId is the one sent to the cryptographic service and written on the operator's audit record. The X-Correlation-Id header of this response is a different one, the id of the browser's request.

A request that was never written is not this type: that is 502 Crypto Playground Runtime Unreachable, and nothing was executed.

Response Example

{
  "type": "https://docs.ankatech.co/errors/crypto-playground-execution-status-unknown",
  "title": "Crypto Playground Execution Status Unknown",
  "status": 504,
  "detail": "Runtime may have executed the operation, and no answer was received. Trace it with its identifier before running it again.",
  "instance": "/api/v3/admin/tenants/8d2f1c4e-3b7a-4e91-a6d5-0c9f2e8b7a14/crypto-playground/execute",
  "extensions": {
    "failureSource": "RELAY",
    "executionStatus": "UNKNOWN",
    "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. Do not run the operation again yet: nothing is retried at any layer, and a second run spends a second use of a limited combination.
  2. Look the identifier up in the audit log's correlation trace. A cryptographic record with that identifier means the operation ran, and the record states its outcome.
  3. With no cryptographic record once the audit trail has caught up, the operation did not complete, and running it again is your decision.

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