HTTP status: activity delete gates failed

This page documents the problem type URI returned when POST .../activities/{id}/delete/ is blocked after evaluating activity delete gates (and after applying any permitted staff_overrides).

Canonical problem type

type: "https://docs.keja.co/troubleshooting/status-codes/activities.delete_gates_failed"

HTTP mapping

Item	Value
Status code	`422`
Content-Type	`application/problem+json`
`title` (problem)	Short human label (for example "Cannot delete activity").
`detail` (problem)	Human explanation; do not parse for automation per RFC 9457.

Problem document shape

{
  "type": "https://docs.keja.co/troubleshooting/status-codes/activities.delete_gates_failed",
  "status": 422,
  "title": "Cannot delete activity",
  "detail": "One or more rules block deleting this activity.",
  "instance": "/api/v1/activities/activities/42/delete/",
  "errors": [
    {
      "code": "activities.delete.active_enrolments",
      "title": "Live enrolments remain",
      "detail": "This activity still has 2 live enrolments. Drop or transfer them first, or confirm an override if you are allowed to.",
      "severity": "blocking",
      "can_override": true,
      "required_permission": "activities.override_delete_active_enrolments",
      "pointer": null,
      "meta": { "live_count": 2, "total_count": 5 }
    }
  ]
}

`errors` items

Same fields as other Cadence gate endpoints (code, title, detail, severity, can_override, required_permission, pointer, meta). See Enrolment gates failed for the full field table.

Known issue codes (activity delete)

activities.delete.active_enrolments: Waitlist or in-range active/casual/trial enrolments still exist.
activities.delete.enrolment_history: Warning; enrolment rows exist; requires attestation when can_override is true.
enrollments.insufficient_permission_to_override: Staff attested an override but lacks required_permission.

For preview, staff_overrides, permissions, and list filtering, see Activity delete gating and staff overrides.