task scheduler does not end after job completion

[peterlecki]

Works fine manually but when used with Task Scheduler, the batch job runs, creates sync.ffs_lock, syncs files successfully, removes the sync.ffs_lock, reports confirms success but the Task does not end in Scheduler and it keeps showing "running". I can force it to end manually and run again which is fine in this case since the lock file was previously removed but if the Task is set to end automatically after some time and the job is not done yet, it will end the task with the sync.ffs_lock still in place so subsequent runs won't go.

[peterlecki]

ping

[xCSxXenon]

Does this actually cause any issues? I have a task that always says running but the task itself runs every day at the correct time without issue. Check task manager and see if FFS is still running, if not, it's fine to leave

[Hikkupz]

it most likely ended but windows stupidly doesn't update the screen. hit F5 and see if it changes.

[kprinsloo]

Goodness gracious I found the solution to this problem today. I've been experiencing this problem for months. What you need to do is, in Freefilesync, when you save the job as a batch job, make sure you tick "Auto-close" and "ignore errors". It will then ensure your tasks in Windows Scheduler go back to "Ready" once the job has been executed.

[Zenju]

FreeFileSync will detect and handle this case automatically in the next version:

FreeFileSync 12.5
------------------------------
Automatically adapt batch options to prevent hanging a non-interactive process (Windows)

Current beta: https://www.mediafire.com/file/5x6o49v71gfohgm/FreeFileSync_12.5_%255BBeta%255D_Windows_Setup%25282%2529.exe

[TomTaTomTomTom]

it most likely ended but windows stupidly doesn't update the screen. hit F5 and see if it changes.

Wooooooow. I can't believe that was it. I am hating that my team chose Windows for their server platform. This should not be a problem in a 2022 version Windows OS.