Comment 9 for bug 1524477

Lingxian,

What you suggest would work. However, it should work now as well if we assume that our transactions and locks work as expected. Workflow controller should have exclusive access to workflow execution object (actually graph of objects related to it), that's why we have a locking mechanism: to prevent concurrent updates of the same workflow execution state. But the thing is that locking mechanism does not work properly, I've done some investigation on that. So your solution would just mask more fundamental problem. That TX/locking problem may also cause other problems, so we need to fix it.