If Egnyte added a SyncInProgress flag to their server metadata, as well as the client side code to keep the file locked when this flag is set to true, this would prevent this from happening in the future.
This relates to a post in the Sharing and Collaboration board found here: https://community.egnyte.com/t5/Sharing-and-Collaboration/Files-unlocking-before-data-changes-sync/m...
Hi @Brian Beaton , Thanks for your suggestion. It is a great idea and we can consider implementation of something similar after weighing the pro/con's of the proposed solution. One issue that I can think off is that if both the users are in the same office and are connected to the Turbo device they will still not be able to access the latest version until the file syncs to the cloud and gets unlocked. Also how this will play out in deployments that have multiple Turbo devices deployed is something we need to think through.
I am just repromoting this suggestion.
Regarding your Turbo comment, if the idea is to ensure that people believe the file is locked while it is uploading with the desktop client/server approach, it seems that the same approach should hold true for the turbo server as well.
It should get the same SyncProgress flag code that the client machines do to ensure that only the most current version gets opened when the file lock releases.
Egnyte transforms business through smarter content allowing organizations to connect, protect, and unlock value from all their content.
If you can't find what you're looking for, contact Egnyte Customer Support.