AnsweredAssumed Answered

Wrong executionId when using Error Boundary Event

Question asked by bkonrad on Mar 10, 2016
Latest reply on Mar 18, 2016 by jbarrez
Hi,

i have a problem getting the correct executionId in a Service Task which has a Error Boundary Event defined:

[img]https://drive.google.com/file/d/0B4B-GQHdB3Xta0dELTJiSVpQRms/view?usp=sharing[/img]
https://drive.google.com/file/d/0B4B-GQHdB3Xta0dELTJiSVpQRms/view?usp=sharing

When the processinstance reaches the wait task, an I want to signal the execution, but the executionId retrieved from Task 1 can not be found in RuntimeService.signal(), when using the processInstanceId for signalling, everything works.

Is there anything wrong or is this a bug?

Regards,
Björn

Outcomes