Instruction: SynchronizedWait - System.Exception: No instance could lead the synchronized SynchronizedWait!

Hi,
last night, my two NINA instances failed to synchronize. Specifically, the secondary instance—which controls only the second OTA and not the mount or the guide—encountered errors on all SynchronizedWait commands except the last one at the end of the session. This has never happened to me before. I tried reading the logs, and it seems there were some issues on both sides, but I can’t figure out what might be causing it. I’m attaching both logs.
The log for the secondary (slave) instance is where the errors are found:
2026-06-19T23:02:13.1825|ERROR|SequenceItem.cs|Run|263|Instruction: SynchronizedWait -
System.Exception: No instance could lead the synchronized SynchronizedWait!

Attached, you will also find the two sequences
Best regards
G

[2026_06_19_\[SLAVE\]_FASTOS_SURVEY.json](https://github.com/user-attachments/files/29161926/2026_06_19_.SLAVE._FASTOS_SURVEY.json)
[2026_06_19_\[MASTER\]_FASTOS_SURVEY.json](https://github.com/user-attachments/files/29161925/2026_06_19_.MASTER._FASTOS_SURVEY.json)

[20260619-220736-3.2.0.9001.3772-202606.log](https://github.com/user-attachments/files/29161873/20260619-220736-3.2.0.9001.3772-202606.log)
[20260619-220943-3.2.0.9001.4952-202606.log](https://github.com/user-attachments/files/29161874/20260619-220943-3.2.0.9001.4952-202606.log)

Start by comparing the attached master and slave log files around the SynchronizedWait errors, then inspect the corresponding attached sequence JSON files. Determine why the secondary instance cannot find a leading instance for these commands, reproduce the failure if possible, and verify that synchronized waits complete without the reported exception.

Written by the indexing model from the issue text.