After further investigation into the cause, the bug seems to have popped up only after I made the points binding on the path two-way using a mechanism similar to the one mentioned here.
I guess what’s happening is the changes to the points in the path are not getting saved in Redux and hence the older path state is getting rendered after a flicker since the skipDiagramUpdate remains false when we are still updating the text on it. So the old path state from Redux is overidding the path updates in the canvas.
That’s why I was asking if there is any event that gets triggered when link path gets changed due to changes in the link port that way I can listen to the path point updates and update that in Redux.