Experience Sandbox Seed Defective
URI: https://docs.ankatech.co/errors/experience-sandbox-seed-defective
HTTP Status: 500 Internal Server Error
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 Experience Center sample data the running release ships cannot be used. The platform tried and could not. 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 failed sandbox create.
- While the sandbox is seeded. If the sample data cannot be used 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. It has its own problem type so that an operator can tell a defective release artifact from a generic internal error. The detail is fixed and names no file, path, size or parser message; the Admin API log names the reason.
A release that ships no sample data at all is a different refusal: Experience Sandbox Seed Unavailable, 403.
Common Causes
- The sample data could not be read from the release.
- The sample data is larger than the size the release reads.
- The sample data is not a document the release reads, or it does not compose and validate.
- The sample data carries an administrator password, which the platform never reads from sample data.
Each cause is a property of the installed release, not of the request.
Response Example
{
"type": "https://docs.ankatech.co/errors/experience-sandbox-seed-defective",
"title": "Experience Sandbox Seed Defective",
"status": 500,
"detail": "The Experience Center sample data this release ships cannot be used. No sample data was written.",
"instance": "/api/v3/admin/platform/experience-sandbox",
"timestamp": 1763112600,
"extensions": {
"requestId": "4f1d8b62-9e3a-47c5-8a2b-6d0e3c7f19a4"
}
}
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.
- Contact support with the
requestId. The installed release's sample data is defective, and a corrected release is the remedy. - 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.