The BPMN Spec mandates that if an Interrupting event subprocess fires, it must make sure that other event subprocesses do not fire as well.
- Create process with two interrupting event subprocesses: one waiting for a message and one waiting for a signal
- Place user task afterm message start event of first event subprocess
- Start process
- Trigger message event subprocess by delivering the message. As a result the process instance is waiting in the user task after the event subprocess
=> If I send the signal now, the second event subprocess triggers. This should not be possible.
The same problem can be experienced with timer events