FWIW, there are no bpms that are firing and causing the interference in this environment. Most likely in this case, it was a user performing some update or transaction that caused the conflict, which means the error would be intermittent. The point is that the code should not be so fragile that the entire process blows up when this happens. Likewise, development should be able to engineer their own scenario to interfere with the process in order to reproduce the issue, and then confirm the fix for the issue is successful, vs. putting the burden on the customer to prove that an issue exists.