AnsweredAssumed Answered

Boundary Error Event on SubProcess not cancelling signal

Question asked by mhanrahan on Jan 14, 2015
Latest reply on Feb 9, 2015 by mhanrahan

As part of our process, we have an inclusive gateway that branches to a Signal Catch Event as well as to a Call Activity.  In normal execution, the child process will signal the parent process and continue on to another inclusive gateway that will continue when both branches are complete.

However, with an exception scenario, that signal is never sent, and an error gets thrown and caught at the edge of the containing sub-process and continues to a human task for fallout handling.  The problem is that the Signal Catch Event is still active, even though the sub process that it is part of has been interrupted by a boundary event.

I have attached an image (just save and remove the .txt at the end) that shows what state the process is in after this has occurred.

So I guess my question is that is this intended behaviour for the process engine or not? If it is, is there a way to get around it so that the signal event is no longer active?

Michael Hanrahan