Any way to kill a Syncovery job when network share fails?

[apd123]

I often need to backup over a VPN to a remote network share. Sometimes the VPN fails mid-session.

When it happens, I need to cancel the Syncovery job. If I click cancel, it then says it is waiting for operations to complete before copying, As the share is down, they never complete. The only way to stop it is to force close Syncovery but that then makes the mac unstable: it will never shut down properly after that and must be forced to shut down, which is a real pain and will eventually damage the file system.

Is there a way of cancelling a job, forcing it to end the job without waiting for existing jobs to complete?

[tobias]

Hello,
currently, the only way is to use Force-Close. This will be improved in version 9. The Mac version should be finished in around two months.

[apd123]

Thanks very much. If we could have a force cancel or the force close could not leave the Mac unstable, that would be great. Otherwise, Syncovery (and Superflexible before it) are fabulous - thanks for all your hard work.

[fletch]

I guess the improvement is now in place, in V10 and later?

I have a job that moves files from a local FTP server (router) to a local folder - parsing the names in a post task that files them in folders by Y/M/D.

The first few test were flawless. Recent runs would hang. When cancelling I'd get the result below. Just wondering what was happening during "waiting on operations". After a short wait, cancel did work.

sc-waiting-for-operation.png (25.33 KiB) Viewed 1108 times

This was the first run, with several files. The first one to hang. I got impaitent and cancelled. Maybe it was busy deleting the files on the server?

sc-ftp-hang.png (7.9 KiB) Viewed 1108 times

[tobias]

I think one of the file transfers may have gotten stuck. I recommend leaving it running. It will eventually time out and retry if necessary.