Inside the new Files On-Demand Experience on macOS

Dear Jack_Nichols + Ankita Kirti 

I would like to echo all the other comments and add that I am disappointed at how the update was rolled out and it also had a huge impact on my business and the way we work. I have wasted a lot of time trying to access my files / troubleshoot the issue including several hours with Microsoft Support who initially seemed unaware of the issue and guided to me to uninstall, switch to the standalone package and just 'wait for it to sync and it will all be fine again'.

Obviously it's not.  I know you say my files are technically 'still there' albeit in a different location but they are not easily accessible and take some time to load.  I also rely heavily on autosave and despite switching to the standalone package it still doesn't work for me which is increases the risk of losing work + don't get the benefit of version history and risk creating conflicting files across devices.  Another thing I notice is OneDrive sync client uses a lot of memory + CPU but isn't 'doing anything' . See screenshot.

Whilst I recognise there may be technical reasons that prompted the change, the way it was rolled out could have been improved. I was caught unaware in the middle of an important project and was unable to access my documents after the update took place (even though you say they are there). I'm lucky to have a decent internet connection when the optical illusion you mentioned was 'processing changes' and 'syncing'.

I switched from the App Store version to the stand alone package but auto-save still doesn't work. I also tried resetting, unlinking, deleting all OneDrive related preference files, restarting the computer, talking to Microsoft Support, but unfortunately still doesn't work. 

Look forward to you rolling out a 'hot fix' ASAP. Please do your best to communicate any important information, required action from users and potential impacts during subsequent roll outs.

Thanks

EDIT - I just noticed that my AutoSave feature is now working again. But seems to be taking up a lot of CPU / RAM to do it. (See screen shots). Still experiencing the issue with pinned files taking long time to appear and then load.