Experience Sandbox Exists
URI: https://docs.ankatech.co/errors/experience-sandbox-exists
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) while a sandbox is already live. A deployment has at most one live Experience Center sandbox.
The check runs after the setup, key-protection backend and rotation policy checks and before the sample data is read, so nothing was created: no tenant, no sample data, no invitation. The refusal is recorded in the platform audit trail as a failed sandbox create: the create was admitted and met a state conflict.
extensions.tenantId names the live sandbox. Two creates sent at the same time are decided by the database: the one that loses answers this same refusal, naming the sandbox the other one created while that sandbox is still live; when it is no longer live, the refusal carries no tenantId.
Common Causes
- The sandbox was created earlier, from the console or by another platform administrator, and was never deleted.
- A create was sent twice, for example a retried request whose first attempt succeeded.
A sandbox that was deleted is closed and no longer counts as live; a sandbox whose sample data failed to provision was closed again and does not count either, unless that closure itself failed: such a sandbox stays live, and this refusal names it so it can be deleted.
Response Example
{
"type": "https://docs.ankatech.co/errors/experience-sandbox-exists",
"title": "Experience Sandbox Exists",
"status": 409,
"detail": "An Experience Center sandbox is already live. Delete it before creating another; nothing was created.",
"instance": "/api/v3/admin/platform/experience-sandbox",
"timestamp": 1763112600,
"extensions": {
"tenantId": "6d1f3a52-8c4e-4b7a-9f20-3e5d7c9b1a46",
"requestId": "9e4c1b7a-6f2d-4a85-b3e9-2c7f0d5a8b16"
}
}
Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.
How to Resolve
- Read the live sandbox:
GET /api/v3/admin/platform/experience-sandbox(operationgetExperienceSandbox). It is the tenantextensions.tenantIdnames. - Keep using it, or delete it with
DELETE /api/v3/admin/platform/experience-sandbox(operationdeleteExperienceSandbox). The delete closes the sandbox tenant through the ordinary tenant closure; its keys are retained and permanently unusable. - Create the sandbox again if you deleted it.
See Admin API endpoints*.
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.