Skip to content

Cascade Subset Violation

URI: https://docs.ankatech.co/errors/cascade-subset-violation
HTTP Status: 409 Conflict

When you see this

A cascading change would leave dependent resources outside the bounds of the policy that governs them. The cascade was rejected to keep child policies a valid subset of their parent.

Common Causes

  • Changing a parent policy in a way that would make existing child policies non-conforming.
  • A cascade that would widen a child policy beyond the new parent bounds.
  • Dependent resources that cannot be brought into compliance by the cascade.

Response Example

{
  "type": "https://docs.ankatech.co/errors/cascade-subset-violation",
  "title": "Cascade Subset Violation",
  "status": 409,
  "detail": "The cascading change would leave dependent policies outside the allowed subset.",
  "instance": "/api/v3/admin/tenants/00000000-0000-0000-0000-000000000001/policies",
  "correlationId": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": 1730000000
}

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

How to Resolve

  1. Identify the dependent resources that would violate the new bounds (the detail field lists the conflict).
  2. Bring those child policies into compliance first, or narrow the parent change.
  3. Re-apply the cascade once all dependents would remain a valid subset.

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