I continue to see cases of where workflowy web stops saving any changes

I'm running Safari 11.1.2 running on OS X El Capitan 10.11.6 using the web version of Workflowy, and for around the past month or so, I've been experiencing a very serious and frustrating problem periodically: At some point, seemingly related to when my network connection drops, then gets reconnected, Worklowy loses the ability to save my local changes up to the master store on the server.

Once this happens it's completely UNRECOVERABLE – all subsequent local changes can still blithely happen, but the button that shows [Save Now] or [Saved] or [Saving] is either permanently stuck in [Save Now] or [Saving] and any changes that I make beyond that point will be LOST FOREVER.

This is one of the most serious and painful bugs that any such application can have, and much as I love Workflowy and use it to organize practically every aspect of my life, I WILL switch to another system if you cannot fix this bug soon!

I've seen other such bug reports, along with assurances from your team that the problem has been fixed… however, even after reloading the page – and discarding ALL my changes :-( – and signing out of my workflowy account and signing back in, and even closing the tab and re-opening it, the saving problem continues to occur, perhaps slightly less frequently over the past couple of days but very much still there – it just happened to me again a few minutes ago.

You need to realize how serious this problem is, no matter whether it is relatively rare or not, ANY kind of data loss, especially one that occurs at the rate of several times PER WEEK is UNACCEPTABLE!

Also when you do fix the problem, please realize that cheery statements like "Oh, just sign out and sign in again and the problem will be fixed" sound especially unempathetic and uncaring when the act of doing this causes the user to LOSE THEIR CHANGES!

I cannot encourage you strongly enough to put your best efforts into pouring through your synchronization and saving code and do EVERYTHING POSSIBLE to make it 100% bullet-proof and robust, no matter what kinds of network errors have occurred.

Your [Save Now] button is especially useless and frustrating as it is NOT some kind of robust backup "I-will-definitely-save-to-the-server-for-sure" thing, but instead it seems to simply trigger the same code used for auto-save, which when the latter is not working, does NOT HELP.

Please don't just make a quick fix; re-plumb your code to be very, very robust in the face of any kind of network error, weird state problems, threading issues, whatever it is – you need to have a fall-back super-robust way of getting local changes up to the server that is unaffected by any problem problems encountered… perhaps you need to close and re-open the connection, perhaps you need to ignore all local state flags saying whether it's time to save or not… whatever you need to do, please at least provide some fall-back method that definitely DOES save changes even if it's slow, to work around any bugs in your "clever and quick" auto-save code.

Thanks very much

-- David Good