Hi @philstopford,
We deployed a change in 3.6.1 where files that are locally deleted while Insync is offline are just unsynced in the cloud. Related topic here. Upon getting feedback that it wasn’t native, we reverted the behavior on 3.7.2, and instead implemented a setting where a user can change said behavior.
What does it do?
- The setting allows you, the user, to choose how to handle local deletions while Insync is offline. By default, 3.7.2’s behavior is to sync the deletions, meaning your cloud files will also be removed once you start Insync after deleting files locally.
Are the cloud contents then just ignored in the future?
- Only if you set the setting to unsync deletions. Otherwise, it will mirror the local deletions.
If so, are they ignored across all machines, or just for the machine where the deletions were made?
- Just for that machine
Why is this recommended for dual boot set-ups?
- This is recommended due to instances in the past where files were incorrectly removed from the cloud (which is why we used to not recommend using the same sync folder for dual boot setups). The aim for this particular setting was to help prevent unwanted deletions for dual boot users.
Recommendation about which option is more robust:
- Did you mean the current options in the
unsync-delete
setting, or Insync as an application in general