Sometimes, but not always, when a batch file is run from Win11 Task Scheduler, the "Last sync" date/time is incorrect.
For example, two batch files that are started from Task Scheduler every night(including successfully last night) currently show 44 and 45 days since last sync. On the other hand, another batch file that was run earlier today from Task Scheduler shows the correct last sync time.
In contrast, any batch file that is started "manually" from the FFS user interface shows the correct time for the most recent run.
"Last sync" sometimes not correct
- Posts: 15
- Joined: 27 Jan 2023
-
- Posts: 4059
- Joined: 11 Jun 2019
- Posts: 15
- Joined: 27 Jan 2023
Thanks for your reply, xCSxXenon. I looked at the thread that you linked, but I don't understand how it applies to my situation.
If "multiple instances" means more than one FFS job running simultaneously, that's not the case for me. The batch jobs that I start from Task Scheduler are scheduled to run one job at a time in a specific sequence. Each job completes before the next one starts, with time to spare.
If "multiple instances" means more than one FFS job running simultaneously, that's not the case for me. The batch jobs that I start from Task Scheduler are scheduled to run one job at a time in a specific sequence. Each job completes before the next one starts, with time to spare.
