We just recently upgraded our Dev environment to 16.0.2. We noticed that processes are triggering even when the start condition is not met.
This is happening for processes with different primary objects. The processes initiate after any save action. Thye sometimes start multiple times.
Clarity 16.0.2
Process definition auto-start conditions not correctly evaluated
Put all processes on hold.
Reactivate them one by one checking if the process auto.start condition is respected
All processes work fine after reactivation