Workload Name Conflict
URI: https://docs.ankatech.co/errors/workload-name-conflict
HTTP Status: 409 Conflict
When you see this
A live (not revoked) administrative workload of the tenant already uses the requested name. Names are compared without regard to case. Nothing was stored.
Common Causes
- A workload with that name exists in the tenant.
- A rename (
PATCH) chose the name of another live workload.
Response Example
{
"type": "https://docs.ankatech.co/errors/workload-name-conflict",
"title": "Workload Name Conflict",
"status": 409,
"detail": "A live administrative workload of this tenant already uses this name. Choose another name, or revoke the workload that holds it.",
"instance": "/api/v3/admin/tenants/7d2f4a10-9c31-4b8e-a5d6-2f11c0b47e93/workloads",
"timestamp": 1730000000,
"extensions": {
"requestId": "550e8400-e29b-41d4-a716-446655440000"
}
}
Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.
How to Resolve
- Choose another name.
- Or revoke the workload that holds the name; a revoked workload releases it.
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.