Details
L3 - Default Description
Context:
Depending on the async before/after boundary of flowNodeInstance it can happen that no flowNodeInstances exist yet when an incident occurs. This causes a lack of flowNodeInstances in cases where there are open incidents on those flowNodes. This is also mentioned in upgrade notes: https://docs.camunda.org/optimize/latest/technical-guide/update/3.1-to-3.2/#limitations
As an example in this flowNodeCount view there are no instances on the `Incidents that stay open` flow node:
Compared with the incidents view on the same process instances reveals the open incidents on this flow node:
Compared to the Cockpit view, for every open incident there is actually a flowNodeInstance counted:
The reason is that Cockpit also counts so called `transitionInstances` that represent these flowNodeInstances in the case of Open Incidents.
AT:
- find a way to count flowNodeInstances for open incidents where no flowNodeInstance exists yet
