Posted: 2016-07-13 18:57
I took me a long time to figure out the 'option batch' affects the 'synchronize' command.
Maybe you could cross-reference the documentation.
My use-case was that I was write-locking existing files on the destination (that had been modified >x days in the past...) and then using a 'synchronize remote -delete'.
However, the task would exit as soon as it would not be able to delete a remote file.
With 'option batch continue' it skips this errors and continues working on the whole list of files to process (e.g. uploading files not yet present in destination) and finally reports error level 1, which is exactly what I was searching for.
You can post new topics in this forum
And it's free!