Currently it's only possible to run a command in one of these cases.
Feature request: extend "run a command" functionality
- Posts: 2
- Joined: 5 Jul 2024
It would be nice to be able to run a different command in case of completion, error or success of the synchronization.
Currently it's only possible to run a command in one of these cases.
Currently it's only possible to run a command in one of these cases.
-
- Posts: 2464
- Joined: 22 Aug 2012
You can realize that yourself, by using a script that evaluates the FFS exit code.
- Posts: 2
- Joined: 5 Jul 2024
First of all, thanks for the suggestion!
I'm currently running a .ffs_batch through the Windows Task Scheduler and executing a .bat file on synchronization success.
The execution of the .bat file is set through the FFS GUI in the previous screenshot.
I could use the exit code as you suggested, but I think that would mean running a .bat file instead of the .ffs_batch file through the Windows Task Scheduler.
The .bat file would then run the .ffs_batch and evaluate its exit code.
I think that being able to set a different command to run in case of completion, error or success of the synchronization through the FFS GUI would be a lot more straight forward.
I'm currently running a .ffs_batch through the Windows Task Scheduler and executing a .bat file on synchronization success.
The execution of the .bat file is set through the FFS GUI in the previous screenshot.
I could use the exit code as you suggested, but I think that would mean running a .bat file instead of the .ffs_batch file through the Windows Task Scheduler.
The .bat file would then run the .ffs_batch and evaluate its exit code.
I think that being able to set a different command to run in case of completion, error or success of the synchronization through the FFS GUI would be a lot more straight forward.
