You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this multiple times. I have a shread md file. Someone edits it on the desktop and sync it back. If i try to open the document later I get this:
with the option to either use the current version or use the saved version.
Also a hard refresh of the browser and re-open the document doesn't help. Maybe some server-side caching? I would expect that I always get the latest version from the storage. The only place where such a comparison makes sense to me is if you have a sync conflict because people edit the file at the same time in the browser and on the desktop. But that's probably also hard to detect...
The text was updated successfully, but these errors were encountered:
schiessle
changed the title
Documents out-of-sync if someone edited it in the desktop
Documents out-of-sync if someone edited it on the desktop
Feb 24, 2022
@schiessle I've shared the file and edited it anonymously. I can still access normally as the main user.
Please let me know if you are still able to reproduce the problem on the latest version.
This may still happen if the file is editing through the desktop but the editing sessions were not properly closed (and cleaned up yet by the background job) or some changes from the web have not been persisted.
Tested on c.nc.com
I noticed this multiple times. I have a shread md file. Someone edits it on the desktop and sync it back. If i try to open the document later I get this:
with the option to either use the current version or use the saved version.
Also a hard refresh of the browser and re-open the document doesn't help. Maybe some server-side caching? I would expect that I always get the latest version from the storage. The only place where such a comparison makes sense to me is if you have a sync conflict because people edit the file at the same time in the browser and on the desktop. But that's probably also hard to detect...
The text was updated successfully, but these errors were encountered: