Invisible sequence flow between boundary event and its task

I found that it is quite easy to accidentally produce an invisible edge between a boundary event and the task its is attached to. This sequence flow is not represented in the diagram but executed at runtime. This may lead to unexpected behaviour.

When you have a task, which also has a boundary event, and then draw a flow from this event back to the task, you end up with an invisible transition, which can only be removed by directly editing the XML.

Is this intended behaviour? If not, can someone open a bug report.

diagram_1.bpmn (1.8 KB)
diagram_1

Ping @nikku ----------

2 Likes