Deletions disabled
Deletions disabled
Hello, I'm still experimenting with Syncovery to understand everything it can do. I've noticed that if I run a profile that tries to delete all the files in the target then Syncovery will refuse. That's OK and I get why. If I keep re-running the same profile with nothing at all changed it eventually goes 'ok then' and deletes everything. Is this supposed to happen? Thanks.
- Attachments
-
- Screenshot 2025-07-27 180541.png (17.72 KiB) Viewed 1756 times
Re: Deletions disabled
Hi,
it depends. Maybe there was one file left. You would need to look inside the log files. It won't delete 100% by default, even if you allow 100%. However, this can be overridden if you really want to.
it depends. Maybe there was one file left. You would need to look inside the log files. It won't delete 100% by default, even if you allow 100%. However, this can be overridden if you really want to.
Re: Deletions disabled
Hi Tobias, the curious thing is it did delete everything on the 4th run for no particular reason I can see, when it refused on the first 3 runs.
Re: Deletions disabled
I've been experimenting some more and there's definitely some inconsistency in how Syncovery behaves, but I'm finding it hard to discern a pattern to it. It refuses several times to delete everything in the target, then seemingly randomly says OK and does it. If I can come up with something reproduceable I'll post it here.
Re: Deletions disabled
Well I suppose it is reproduceable. All I'm doing is repeatedly running a profile that has been given permission to delete everything at the target end. Keep clicking the play button and it often refuses 3 times because deletions are disabled (they are not) then just does it on the 4th. No changes at all made to the profile. No files deleted until it decides, apparently randomly, to delete them all. The inconsistency is baffling.
Re: Deletions disabled
Thanks, I will look into it!
Re: Deletions disabled
Did you find anything unusual?
Re: Deletions disabled
I cannot confirm the problem. You should start such jobs in Attended Mode and confirm the deletions.
I will test it once more on ASUS directly but it's unlikely that I will be able to produce the same issue here.
I will test it once more on ASUS directly but it's unlikely that I will be able to produce the same issue here.
Re: Deletions disabled
OK, I accept it's not a massive problem. It's just the inconsistency that bothers me. As a last try, I'm attaching the profile I'm using. For me it's easy to recreate. Keep running it and 3 or 4 tries in it suddenly decides it's OK to do the deletes.
Re: Deletions disabled
One thing I have observed. If the source directory is not empty then Syncovery seems to behave correctly and consistently. This odd behavour seems to happen when the source directory is empty.