Merging two boundary events causes issues with grid and connections
Describe the Bug
There seems to be a serious issue when trying to merge to boundary events into an element.
Steps to Reproduce
- https://bpmn-io.github.io/bpmn-auto-layout/
- Model the process shown above.
Expected Behavior
I expect this process to be layouted cleanly.
Environment
https://bpmn-io.github.io/bpmn-auto-layout/
Adding to ready state. Just to confirm, is this the realistic use case where both the intermediate events are directed towards single end event?
It does not need to be an end event. It can be any element:
Thus, if you have two types of events (message + message, message + timer,...) that are followed by the same element, this error will occur.
This happened to our AWS colleagues while testing the BPMN co-pilot.
done
@till-stadtler fixed