Just for the holiday we got a strange issue that from the CVAD side and MCS updates the interactions wouldn’t work anymore and that machines would stay on and no power cycle actions would be working throughout the night for the daily reboots.
After a troubleshoot with the customer we found out that one of the hypervisor hosts (Hyper-V) got an update in the middle of the night and flipped to the future as of 2025 and within the hour reverted itself. The entire flip caused that the DB was in a filthy state and never recovered to the state of 2024 the current date and time. Opened up a support case for the issue and not many helpful insights there so we decided to move further and recover from a database and snapshot revert (veeam) to a working previous state. This all resolved the issue but also triggered the missed scheduled reboots as after the restore (so the maintenance schedule for the weekend was a good point for us and the customer)
Never can stress enough that back-ups are needed!
Hope it helps.