There was an instance towards the start of a lock stretch overnight where the SQZ angle railed and did not fix itself until 22 minutes later, all while H1 remained observing with BNS range between 40-80 Mpc.

The SQZ angle railed at 08:10:01 UTC, SQZ_MANAGER showed a notification "SQZ angle is out of range. If SQZ looks bad, request RESET_SQZ_ASC_FDS and then FREQ_DEP_SQZ", and the BNS range dropped to around 42 Mpc. At the end of my shift last night, the same thing happened and I was able to reset the angle and return to observing (alog83384), but no one was actively monitoring H1 at this time, so the SQZ angle remained railed at 276.86 deg until it flipped to 0 deg 7 minutes later and the range improved to around 80 Mpc. Then, 13 minutes after that at 08:30:55 UTC, the SQZ angle finally starts moving positive, eventually settling around 180 deg and recovering the BNS range back to about 160 Mpc. The SQZ angle stayed steady for the rest of the lock. The SQZ Guardians did not change states during this time of poor range, and I can't glean from the logs what may have been the issue here.