Experience Sandbox Seed Unavailable
URI: https://docs.ankatech.co/errors/experience-sandbox-seed-unavailable
HTTP Status: 403 Forbidden
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 running release ships no Experience Center sample data. The deployment does not offer the sandbox, so the create is refused. The response carries no Retry-After: no retry against the same release succeeds.
The sample data is read twice:
- Before any tenant exists. After the live-sandbox check, the create verifies that the sample data can be read and composed. A refusal here creates nothing: no tenant, no sample data, no invitation. It is recorded in the platform audit trail as a denied sandbox create.
- While the sandbox is seeded. If the sample data is found missing once the sandbox tenant exists, nothing of it is written, the create is recorded in the platform audit trail as a failed sandbox create naming the sandbox, and the sandbox is closed again through the ordinary tenant closure, so it does not count as live. Should that closure itself fail, the sandbox stays live and the answer is still this refusal.
Either way no sample data was written, and no invitation was sent. The detail is fixed and names no file or path.
Sample data the release ships and cannot use is a different refusal: Experience Sandbox Seed Defective, 500.
Common Causes
- The running release ships no Experience Center sample data.
Response Example
{
"type": "https://docs.ankatech.co/errors/experience-sandbox-seed-unavailable",
"title": "Experience Sandbox Seed Unavailable",
"status": 403,
"detail": "The Experience Center sample data is not available on this deployment. No sample data was written.",
"instance": "/api/v3/admin/platform/experience-sandbox",
"timestamp": 1763112600,
"extensions": {
"requestId": "a9c3e7b1-2d6f-4f58-b1e4-8c0a5d3f7e26"
}
}
Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. The detail is the same in both cases above.
How to Resolve
- Do not retry: the same create answers the same way until the installed release changes.
- Check the release installed on the deployment. A release that offers the Experience Center ships its sample data; contact support with the
requestIdif yours should. - Read
GET /api/v3/admin/platform/experience-sandbox(operationgetExperienceSandbox). It answers404when no sandbox is live, which is the usual outcome. If it names a sandbox, its closure after the failed seed did not complete: delete it withDELETE /api/v3/admin/platform/experience-sandbox(operationdeleteExperienceSandbox).
See Admin API endpoints*.
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.