Camunda incident
Cluster updates result in cluster remaining in Updating or Unhealthy status
Camunda experienced a minor incident on October 28, 2025 affecting Operate and Tasklist, lasting 4h 19m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 28, 2025, 11:42 AM UTC
We are currently investigating alerts of stuck updates. The health information in our SaaS Console calculates that the update process is ongoing. However, the update is already finished. We identified that the health logic incorrectly takes into account the legacy importer from the prior version. Impact: Incorrect health states in our SaaS Console and issues by dependent systems that take the health state into account. Affected Versions: Clusters that were updated to SaaS Generation 8.8gen2
- identified Oct 28, 2025, 12:51 PM UTC
We’ve identified an issue with the health evaluation logic in our Control Plane and are actively working on a fix. In the meantime, we’re manually triaging affected clusters to move them out of the “Update” state. The Camunda cluster itself is available and not affected from this.
- identified Oct 28, 2025, 01:28 PM UTC
We have developed a fix addressing the Control Plane health logic issue. The update is currently being tested and validated in our development and staging environments to ensure stability before production release. We’ve also completed triage of all Enterprise clusters to ensure the issue is not affecting the interactions in our SaaS Console.
- resolved Oct 28, 2025, 04:02 PM UTC
The incident has been resolved. The fix has been successfully deployed to all production systems, and normal operation has been fully restored.