Workflow connections become visually obscured by intermediate nodes

[bigbeka]

The attached image demonstrates two functionally identical workflows.

In Scenario A, node3.a has two incoming connections:

• node1.a → node3.a
• node2.a → node3.a

However, because node2.a sits directly between node1.a and node3.a, the connection from node1.a to node3.a is drawn behind node2.a and is almost completely hidden. At a glance, it appears as though only node2.a is connected to node3.a.

In Scenario B, the nodes are positioned slightly differently, but the workflow is otherwise identical. Here, both incoming connections to node3.b are clearly visible, making the execution flow much easier to understand.

In Scenario C, node connections are correct and the arrow from node1.c pointing at node2.c is solid black colour and no overlap.

Problem

When connections pass behind other nodes, they can become effectively invisible. This makes it easy to overlook additional incoming connections during workflow editing or debugging.

In the example above, it appears that node3.a is only triggered by node2.a, when in reality it is triggered by both node1.a and node2.a.

As a result, node3.a executes twice:

1. Once when node1.a completes.
2. Again when node2.a completes.

Because the direct connection is hidden, this behaviour can be confusing and difficult to diagnose.

Suggested improvement

Improve connection rendering so that overlapping connections remain visible, for example by:

• Drawing connections above nodes while editing or when selected.
• Highlighting all incoming and outgoing connections when a node is selected.
• Providing a visual indication that a node has multiple incoming triggers, even if one of the connections is obscured.

This would make workflows significantly easier to read and reduce the chance of accidentally overlooking additional execution paths.