35 ms·
They really ought to coordinate with users in circumstances like these. What if you'd already begun to fix it - would your efforts have been rolled back? Or i
by rkagerer 3y ago
They really ought to coordinate with users in circumstances like these. What if you'd already begun to fix it - would your efforts have been rolled back? Or if you just happened to use the opportunity to undertake a big cleanup / organizational overhaul on your folder structure?
- 015a 3y agoYeah I'm really not sure, except that I definitely did not receive any communication about what happened (this was back in ~May this year). I also did not proactively reach out to Support (busy that day, had backups, and it was fixed by the next day so). Also to clarify; while its technically possible that the Cloud Sync application on my Synology NAS could have done it; it can be configured with bi-directional sync and is fully authenticated to commit files back to Google Drive and delete existing ones. I have it set to "Download Remote Changes Only" and always have; and while a software bug there could have caused it, the files that re-appeared were long, long deleted to me, everywhere, and I didn't have copies of them on the NAS. Very nice to have them re-appear for a day and get pulled down for actual long-term backup locally though!
- londons_explore 3y agoIn the support forum they were pretty clear to "don't touch the root folder while our engineers investigate".