Skip to content

Workload Revoked

URI: https://docs.ankatech.co/errors/workload-revoked
HTTP Status: 409 Conflict

When you see this

The operation would change an administrative workload that is REVOKED. Revocation is terminal: the record is kept so the audit trail can still name it, and it can no longer be renamed, reactivated, given keys, bindings or scopes.

Common Causes

  • Reactivating a revoked workload.
  • Registering or rotating a key, binding a subject or replacing the scopes of a revoked workload.
  • Renaming a revoked workload.

Response Example

{
  "type": "https://docs.ankatech.co/errors/workload-revoked",
  "title": "Workload Revoked",
  "status": 409,
  "detail": "The administrative workload is revoked, which is terminal. Register a new workload instead.",
  "instance": "/api/v3/admin/tenants/7d2f4a10-9c31-4b8e-a5d6-2f11c0b47e93/workloads/9b2f6c1e-3d4a-4c8b-a1e7-5f0d2c9b8a71/reactivate",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

  1. Register a new workload, give it a new key and the scopes it needs, and update the automation that used the revoked one.

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