Event-Based Gateways looping back to events throws a parsing error

Consider a scenario such as:

Setups like this cause an error: Engine Parser returns something like : PVM Exception: duplicate activity id IntermediateCatchEvent_432432.

Can someone explain why a second event gateway cannot point back to a event used by another gateway?

The BPMN specification disallows this as follows:

I guess the engine does not properly validate this case, so it doesn’t throw a better exception. Same goes for the modeler.


@thorben do you know the reasoning behind this? (from the bpmn spec perspective)

Not really. My guess is that this is easier to implement that way.