Hi! I noticed that when pod becomes unhealthy and restarts for any reason in self-hosted Zeebe cluster leader failover process that follows occasionally results in duplicate process instances being created (1 by old leader before it failed and 1 by new leader). All our process instances have unique IDs in one of the variables so it’s clear that duplication happens in engine. Is it expected behaviour, a bug or an issue with how our cluster configured?
1 Like
I have faced the same issue with Camunda 8.4.1.
Looks like it is actually an issue. in case of leader fail over this happens
1 Like
I also have faced same issue with Camunda 8.2.8