[Veeam Backup for Microsoft 365] Job did not start on schedule

[aeph]

Hi everyone,

Earlier this week, we experienced an unexpected server shutdown. After the shutdown, I had to restart the proxies and services (Veeam + NATS). I even had to terminate one job using PowerShell with the `-Force` parameter because it could not be stopped through the GUI.

After restarting everything, all jobs ran successfully again. However, we are now facing a new issue: the jobs only run correctly for a single day. After 11:59 PM, no scheduled jobs start anymore, and they all fail with the following error:

**[Veeam Backup for Microsoft 365] Job did not start on schedule.**

As a result, I have to restart all proxies every morning to get the jobs running again. After the proxy restart it takes 1-2 minutes and than the queued jobs are start running (the jobs that are still in the retry phase and haven't completely failed yet).

The proxies themselves remain online, but I suspect that something may have become stuck in the NATS queue as a result of the unexpected shutdown.

Is there a way to reset the proxies or clear the cache (or perform a similar cleanup) to prevent the proxies from getting into this state? Restarting all proxies + management console the same time did not solve the issue.

[Polina]

Hi aeph,

Please report this issue to support. In my opinion, there're multiple things to investigate - from the unexpected shutdown to the need for proxy restart.
Also, please post your case ID here for the followup.

Thanks!