ID 611675 - Reconnecting Media during a Sync Session can cause the kClipKnobChanged event to trigger continuously

Problem summary:
Reconnecting Media during a Sync Session can cause the kClipKnobChanged event to trigger continuously 
 
Customer reported version:
Hiero Player 15.1v4
 
Customer reported platform:
Alma 9
 
Steps to reproduce:
1) Download the attached TestClip.mov and TestClipCopy.mov and launch two separate instances of Nuke Studio
2) In one instance, navigate to File > Import File(s)... and select the TestClip.mov
3) Drag this Clip to the Timeline to create a new Sequence
4) Open the Sync Session panel and Host a session
5) In the other instance of Nuke Studio, open the Sync Session panel and Connect to the current session
6) From either instance of Nuke Studio, open the Script Editor and execute the following code:

def clip_knob_changed(event):     print(f"Knob changed: {event}") hiero.core.events.registerInterest("kClipKnobChanged", clip_knob_changed) 

7) Without changing your Nuke Studio instance, right-click the TestClip's TrackItem and navigate to Clip > Reconnect Media...
8) Select the downloaded TestClipCopy.mov file and observe how the kClipKnobChanged event is continuously triggered: 

 
Expected behavior:
The kClipKnobChanged event should only fire when a knob has been changed and not loop repeatedly.
 
Actual behavior:
If a Sync Session has at least two users, Reconnecting Media can cause the kClipKnobChanged event to trigger endlessly.
The same behavior occurs when utilizing the .reconnectMedia() Python method instead of Reconnecting Media via the UI.
 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
Nuke Studio 16.0v7 - Windows 11, macOS 14 Sonoma
Nuke Studio 15.1v1 - Windows 11
Nuke Studio 15.0v8 - Windows 11
Nuke Studio 15.0v5 - Windows 11, macOS 14 Sonoma -- Regression
 
Unable to reproduce bug in:
Nuke Studio 15.0v4 - Windows 11, macOS 14 Sonoma
Nuke Studio 15.0v1 - Windows 11
Nuke Studio 14.0v1 - Windows 11
Nuke Studio 13.0v1 - Windows 11
 
Earliest version tested:
Nuke Studio 15.0v4 - This issue doesn't appear in this version and has regressed