Scheduled backup does not start until Veeam services are restarted

[NicoDussan]

Hi,
I am seeing a reproducible scheduling issue with Veeam Backup for Microsoft 365 Community Edition.

Veeam Support Case #08206338

Environment
- Veeam Backup for Microsoft 365 Community Edition
- Version: 8.5.0.1014 P20260622
- Windows 11
- One back up job
- Daily schedule: 16:00

The job is enabled and the schedule is active.

On two consecutive days, the scheduled backup did not start even though:
- The PC was powered on and awake;
- Veeam.Archiver.Service was Running;
- Veeam.Archiver.Proxy was Running;
- The job remained enabled;
- No backup session was created in History.

In both cases, after the scheduled time had passed, NextRun remained stuck at the already expired scheduled time instead of advancing to the following day.

Restarting Veeam.Archiver.Proxy and Veeam.Archiver.Service immediately caused NextRun to recalculate to the next day. The missed backup was not executed retroactively.

After the first service restart, I changed the schedule to a later time the same day as a controlled test. The job then started automatically at the expected time and completed successfully. However, the same scheduling failure reappeared the following day.

I also verified that the machine was not sleeping or restarting around the scheduled time, and Windows Task Scheduler does not contain a Veeam task responsible for launching this job.

Veeam service logs show that the service remained active and continued processing internal messages around the scheduled time, but no backup session was started.

The issue has therefore been reproduced on two consecutive days and restarting the Veeam services temporarily restores normal scheduling behavior.

A Veeam Support case is already open:
Case #08206338

The support log package covering 24–26 August 2026 and screenshots showing the expired NextRun state before service restart have been uploaded to that case.

Has anyone seen this behavior with 8.5.0.1014, or is there a known issue/hotfix related to scheduled jobs not being triggered while the Veeam services remain in Running state?

Thanks.

[NicoDussan]

Update:
Support Case #08206338 was automatically archived before technical review due to limited support staff availability for Community Edition cases.

The full support log package covering 24–26 August 2026, together with screenshots documenting the expired NextRun state before service restart, had already been uploaded to that case.

I have now escalated the matter through Veeam Support Management under Escalation #ESC0165382, requesting a technical review of the evidence already collected.

The issue remains reproducible: on two consecutive days the scheduled job did not start while the PC was awake, the job remained enabled, and both Veeam services were in Running state. NextRun remained stuck at the expired scheduled time. Restarting Veeam.Archiver.Proxy and Veeam.Archiver.Service immediately caused NextRun to advance to the following day without executing the missed backup.

Any insight from the Veeam R&D team as to whether this behavior matches a known issue in version 8.5.0.1014 would be greatly appreciated.

[NicoDussan]

Update:

Following Veeam Management Support's recommendation, I activated a 30-day Evaluation License on the existing installation and opened a new technical support case specifically for this scheduling issue: Case #08215788.

The relevant Veeam support log package and screenshots documenting the expired NextRun state before service restart and its recalculation immediately after restarting the Veeam services have been uploaded to the new case.

In parallel with the support investigation, I would still greatly appreciate any input from the Veeam R&D team or other users who may have seen similar scheduler behavior in version 8.5.0.1014.