AnsweredAssumed Answered

Error End Event Change in 5.15

Question asked by gokceng1 on Apr 13, 2014
Latest reply on Apr 14, 2014 by trademak
We've been using error end events in sub-processes and main processes since 5.11. In those versions, having an error end event in a main process was just a trivial thing. I've noticed that in 5.15 ErrorPropagation class is re-written and at line 69, execution is checked against null.

My process has only 2 steps: one none start event and one error end event(it is a dummy process just for checking 5.15). In this case I'm getting 'No catching boundary event found for error with errorCode' exception when process is about to complete. I don't think it is a correct behavior. In 5.14 or older versions this was working.

What should I do to make it work again?