Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File sync and Duck Status -- out of sync #10910

Closed
cyberduck opened this issue Dec 17, 2019 · 1 comment
Closed

File sync and Duck Status -- out of sync #10910

cyberduck opened this issue Dec 17, 2019 · 1 comment
Labels
bug core thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

1609ea0 created the issue

One of our employees is updating some files on our WebDav server. It may be an edit to the file internally (excel) or it may be a change to the filename. At times she is on a slow connection and knows she needs to wait for things to finish syncing before severing the connection. When editing many files in many different folders, it is unrealistic to go back into 30 folders and check to see if the sync icon has disappeared.

I told her to just check the MountainDuck status by right-clicking at the bottom right and she has done that. She waits until it says "Up to date". In reality, it is not done yet even though it states "Up to date".

I have found by checking the files on our WebDav file server and can verify that they are not yet up-to-date. This tells me that the sync symbol on the files seems to be accurate, but your overall status (see the picture, bottom right) says it is. This is a problem/bug. How can we help get this fixed?

Thanks for your help.

(running the current version on windows 10 pro. Web server is WebDav running on an also current Synology NAS).


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please reach out to [mailto:support@mountainduck.io] with this bug report.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug core thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

1 participant