This is a clearly repeatable massive flaw in OneDrive that makes its use in business so dangerous...
A few days ago, I had a big sort out of my OneDrive folder structure - deleted lots of documents and folders and, more importantly, moved things around, created new folders, moved files into their etc. General housekeeping.
My main PC a new build with a new Ryzen 3000 CPU and motherboard - where everything is a bit fresh and therefore a little unstable. NOTE: this is nothing to do with the bug I'm reporting here but just setting the scene. Today I installed the latest AMD Radeon driver and I wasn't happy with the installation - as I said, new build.
So I restored my PC to an image I took on 9th September - an image created by Macrium Reflect. This is a pretty common scenario in development and test environments. Same thing might happen if you use virtual machines and restore an earlier snapshot.
The flaw: this restored version of OneDrive (only a few weeks old) decided it was the master (!) and undid all those changes I'd made above - it restored OneDrive back to the 9th September. This is a horrible bug.
Fortunately, in this instance, I spotted it quickly and was able to use the "Restore OneDrive" feature in Office 365 - to restore it back to just before the PC image was restored. But I might not have spotted it for a few days whereby I'd then have out of date stuff melded in with modified files.
This bug is highly repeatable and has been present for several years.
Needless to say, Google Drive and Dropbox which were also restored in that image did not exhibit the same bug. They have better algorithms for tracking changes obviously.
And please, please, please don't suggest UserVoice... that's for feature requests. This is a massive bug and makes working with images and/or virtual machine snapshots a real risk.