After creating a new process with OR conditions and creating an object instance that meets the first condition, the process instance runs into the second condition unexpectedly.
There is a process step with two post-conditions pretty much opposite: one checking some boolean fields to be true while the second one looks to the same attribute values being false.
Occasionally, even if the first post.-condition is met, the process goes through the second post-condition that is not met.
What can be the reason for this erratic behavior?
The process definition was somehow corrupted
Create a new version of the process definition