Skip to content

Experience Sandbox Rotation Policy Refused

URI: https://docs.ankatech.co/errors/experience-sandbox-rotation-policy-refused
HTTP Status: 409 Conflict

When you see this

A platform administrator asked to create the Experience Center sandbox (POST /api/v3/admin/platform/experience-sandbox, operation createExperienceSandbox), and the deployment's effective rotation policy does not admit both rotations the Experience Center walks through:

  • a rotation from a classical algorithm to a post-quantum one (allowClassicalToPqc);
  • a change of algorithm family (allowDifferentFamily).

The policy is read when the request arrives, after the key-protection backend check and before the live-sandbox check, so before any tenant exists. Nothing was created: no tenant, no sample data, no invitation. The refusal is recorded in the platform audit trail as a denied sandbox create.

Common Causes

  • The SAME_FAMILY_ONLY policy template is applied to the deployment: it keeps every key within its algorithm family.
  • The STRICT_SECURITY policy template is applied to the deployment.
  • The deployment rotation policy was edited to set allowClassicalToPqc or allowDifferentFamily to false.

The rotation policy of a new installation, and the DEFAULT template, admit both rotations.

Response Example

{
  "type": "https://docs.ankatech.co/errors/experience-sandbox-rotation-policy-refused",
  "title": "Experience Sandbox Rotation Policy Refused",
  "status": 409,
  "detail": "The deployment's rotation policy does not admit the rotations the Experience Center walks through: a classical to post-quantum rotation and a change of algorithm family. Nothing was created.",
  "instance": "/api/v3/admin/platform/experience-sandbox",
  "timestamp": 1763112600,
  "extensions": {
    "requestId": "3e7a1c9d-4b2f-4d8e-a6c5-9f1b2d7e4a30"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. The detail names only the two admissions; it carries no other value of the policy.

How to Resolve

  1. Read the deployment rotation policy: GET /api/v3/admin/platform/deployment/policies/rotation (operation getDeploymentRotationPolicy).
  2. Set allowClassicalToPqc and allowDifferentFamily to true with PUT /api/v3/admin/platform/deployment/policies/rotation (operation setDeploymentRotationPolicy, scope admin.policy.deployment.rotation.write). The change applies to every tenant that inherits the deployment policy, not only to the sandbox; see Policy Management*.
  3. Create the sandbox again.

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

* restricted content — see higher-tier documentation