I remember having the same issue some time ago at my company, even with individual task status workflow. But still Tactic version 4.3 if I'm not mistaken, as our IT is normally totally overloaded.
We usually work/worked around this, by avoiding connections between the tasks. You can still have a custom order of these task, by putting them from left to right in the workflow editor. Sadly just a workaround, so good to see some inside about this.
Maybe this is not very helpful for the issue here, but I remember having already approved tasks set back to handout or something, if the task before was re-opened and approved again. "update_dependent_tasks" sounds fitting as well.
Eric, if you run in Debug mode and on that function introduce a syntax error or raise an exception under a controlled condition (if you have to do it on a production server) and get the stack trace and post here, we can quickly diagnose how to get rid of that trigger.
08-03-2020, 02:37 AM (This post was last modified: 08-03-2020, 02:41 AM by EricTsuei.)
(08-01-2020, 03:19 PM)remkonoteboom Wrote: Eric, if you run in Debug mode and on that function introduce a syntax error or raise an exception under a controlled condition (if you have to do it on a production server) and get the stack trace and post here, we can quickly diagnose how to get rid of that trigger.