AnsweredAssumed Answered

Timeout firing after execution leaves sub-process?

Question asked by blezek on Jul 3, 2017
Latest reply on Jul 4, 2017 by daisuke-yoshimoto



  Please see the attached diagram.


I have a workflow that uses a subprocess.  The subprocess waits for a set of series to arrive (labeled #1, see the associated question), when everything is ready, the workflow should proceed to the plugin (a JavaDelegate, labeled #3).  But the plugin takes longer than the sub-process timeout (labeled #2) and the workflow exits (labeled #4) through the timeout branch, not the "plugin" branch.


If the "plugin" is async, all works well, but if not, the sub-process timeout fires and the workflow exits unexpectedly.  I would not have expected this behavior.


Should Activiti detect that the execution has left the sub-process and cancel the timeout?