As you can see in the screenshot, I have a batch file that I have created, and it does not report a "last sync" value:
I am running MacOS Sonoma, and since Automator has been deprecated (though it still exists), I do not use the triggering method outlined here on the FFS site.
Instead, I used the new(ish) ShortCuts app and created the following Shortcut:
I then use an app called Shortery to create a schedule for triggering the shortcut which in turn triggers the FFS batch file. This seems to work fine, but FFS doesn't report a "last sync" value, which I would think it would.
Am I missing something here?
Batch file doesn't report last run date when scheduled
- Posts: 17
- Joined: 19 Aug 2020
-
- Posts: 2946
- Joined: 22 Aug 2012
FFS stores this type of information in your GlobalSettings.xml file.
Potential cause 1):
As stated in the linked manual page:
"this file is read once when FreeFileSync starts and saved again on exit."
When your scheduled FFS task ends, it will update the GlobalSettings.xml file. However, if another FFS instance was open while the scheduled FFS task ends, this will not show up in your open FFS instance (because GlobalSettings.xml is only read once when FreeFileSync starts).
Even "worse", when that open FFS instance is then closed, it will save the GlobalSettings.xml file on exit, thereby overwriting the update made to that file by your scheduled task.
In this aspect, FFS is presently not robust against multiple FFS instances being open simultaneously.
Potential cause 2):
The GlobalSettings.xml file and its location are user specific.
I don't know MACs, but in Windows scheduled tasks run by default as the System user, which is different from the logged-in user when you open an FFS GUI. Make sure your scheduled task runs under the same credentials as when opening an FFS GUI.
Potential cause 1):
As stated in the linked manual page:
"this file is read once when FreeFileSync starts and saved again on exit."
When your scheduled FFS task ends, it will update the GlobalSettings.xml file. However, if another FFS instance was open while the scheduled FFS task ends, this will not show up in your open FFS instance (because GlobalSettings.xml is only read once when FreeFileSync starts).
Even "worse", when that open FFS instance is then closed, it will save the GlobalSettings.xml file on exit, thereby overwriting the update made to that file by your scheduled task.
In this aspect, FFS is presently not robust against multiple FFS instances being open simultaneously.
Potential cause 2):
The GlobalSettings.xml file and its location are user specific.
I don't know MACs, but in Windows scheduled tasks run by default as the System user, which is different from the logged-in user when you open an FFS GUI. Make sure your scheduled task runs under the same credentials as when opening an FFS GUI.