Camunda experienced a critical incident on February 16, 2024 affecting Zeebe, lasting 2h 30m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Feb 16, 2024, 03:42 PM UTC
Camunda versions 8.2.22 and 8.1.23 suffer from a critical bug camunda/zeebe#16406 that can result in a Zeebe broker being unable to start if at least one DMN Model is deployed. We have disabled the update path to those Generations as well as removed them from the stable channel. Some clusters are already running those Generations. An emergency Generation to be released soon and we will update those clusters once the emergency Generation is live. We plan to release a GA Generation containing the 8.2.23 and 8.1.24 releases of all components at beginning next week.
- identified Feb 16, 2024, 03:44 PM UTC
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
- resolved Feb 16, 2024, 06:12 PM UTC
All clusters which have been running the Generations suffering from the critical bug camunda/zeebe#16406 have been updated to one of two emergency Generations `Camunda 8.2.22 with Zeebe 8.2.23` or `Camunda 8.1.23 with Zeebe 8.1.24`. These are not endangered to run into this issue anymore. An all component 8.2.23 and 8.1.24 Generation will be released early next week and update paths enabled from existing 8.2.x and 8.2.x Generations.