Um… I’m seeing this on a note that is (I presume, I haven’t actually checked) open on my Mac, which I’ve not used/logged into since last night sometime, and an iPad which I’m actively using now. There are literally hours worth of time between when I would have edited on the mac and what I’m working on now on my iPad. Server based or not, there’s absolutely no reason (short of really really lazy programmers) that the app and back end server can’t intelligently be syncing changes with that much time differential. Changes - and sub-document level changes - should be time stamped. Any modern computer or device should be able to get down to microsecond resolution, frankly, but with humans as the editors, you don’t even really need that.
Further, I’m going to call BS on your “the server can’t read” — sure it can. It doesn’t need to understand whats in the note, just highlight the changes, ALA the “diff” command thats existed on Unix for forever (or small values of, which approximate, forever).
And, busy? Again, calling BS. This worked in the past, has worked well for years. Its not working now. It needs to be fixed. EN will lose users (me among them) if they can’t get basic stuff like this right. If fixing it means they need to buy a few more flops from their cloud provider, then then need to buy a few more flops from their cloud provider, or hire capable programmers and support people. Quit making excuses.