Cases in Kestra 2.0: Manage Incidents All In One Place

Kestra 2.0 introduces Cases, an Enterprise and Cloud feature that turns workflow executions, alerts, approvals, and remediation actions into centralized, auditable incident records within the orchestrator. Cases group repeated failures into a single incident with linked executions, assigned owners, watchers, acknowledgement and resolution SLAs, notification controls, status timelines, and required resolution reasons, while continued failures remain detected even after acknowledgement. They can be created from failed executions, successful-but-suspicious outcomes such as data-quality variances, external webhooks, approval workflows, and planned maintenance windows, with deduplication and auto-linking options to prevent alert floods. Operators can run predefined remediation flows directly from a case, preserving execution links and RBAC controls, while approvals can be tracked alongside HumanTask pauses. Cases uses Kestra’s existing primitives and permissions model, offers in-app notifications, and is positioned as an incident record rather than a full paging or ticketing replacement, as it currently lacks on-call rotations, escalation policies, and external ticket synchronization.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.