In prior releases (e.g., 7.18.0), the NodeInstanceLog connection identified the sequence flow.

After upgrading to 7.53.0, we found that NodeInstanceLog connection identifies the sibling node on the other end of a sequence flow rather than the sequence flow itself.

Current documentation states that the NodeInstanceLog connection is 'Actual identifier of the sequence flow that led to this node instance' which is consistent with previously observed behavior.

Please advise if there's a workaround available to find the sequence flow connecting two nodes.