Hi all! This is an expected behavior, and I am sharing with you the email I sent to one of our users. It includes a (hopefully) detailed explanation of this sync behavior as well as what our team plans to do moving forward:
Thank you very much for emailing about this. I have spoken to our engineers and it looks like I didn’t realize sooner that these reports on the behavior is in fact expected. If you take a look at the release notes on 3.6.0, we implemented an improvement where files that are locally removed (while Insync is offline) will be unsynced in the cloud as a way to support unwanted deletions for certain use cases. The notes can be found in-app - go to the 3 dots on the upper right > Help > click “Release Notes” on the left panel.
However, we realized further that this is not native to users who actually intend to remove such files, hence users reporting the unusual behavior. While we aim to prevent data loss as best as we can, we also want users to continuously have a seamless experience; I’ve requested an improvement to cater to both cases - those who want to delete and those who accidentally delete files while Insync is offline.
Hoping that this info helps and sheds light on what’s been going on with Insync. Would you like to be informed once the improvements have been deployed?