Upgrade StorageError while syncing (Report ID: 716863947)
After it has worked like a charm ever since I started using Zotero, since today, I get an error when syncing my library:
"A file sync error occurred. Please try syncing again."
Sometimes it also syncs forever resp. until I close Zotero. It seems like the syncing process gets stuck somewhere.
I have automatic sync disabled as it slows everything down too much. So, I get the error, whenever I hit the sync button. Interestingly, I only get this error message on one of my devices. The others seem to sync fine.
I have restarted Zotero and rebooted my PC but I still get the error message.
In case it is relevant: When I hit the sync button and i hover above the sync icon, the tooltip keeps saying "Syncing files in My Library (3 remaining)". However, I can see that my latest changes (adding annotations in PDFs and deleting saved searches) did get synced. Or at least, I think, those were my last changes...
Any pointers on how to resolve this error are much appreciated!
"A file sync error occurred. Please try syncing again."
Sometimes it also syncs forever resp. until I close Zotero. It seems like the syncing process gets stuck somewhere.
I have automatic sync disabled as it slows everything down too much. So, I get the error, whenever I hit the sync button. Interestingly, I only get this error message on one of my devices. The others seem to sync fine.
I have restarted Zotero and rebooted my PC but I still get the error message.
In case it is relevant: When I hit the sync button and i hover above the sync icon, the tooltip keeps saying "Syncing files in My Library (3 remaining)". However, I can see that my latest changes (adding annotations in PDFs and deleting saved searches) did get synced. Or at least, I think, those were my last changes...
Any pointers on how to resolve this error are much appreciated!
-
dstillmanThis should be fixed now in Zotero 7.0.15. (It could happen starting in 7.0.14 if a download took longer than 30 seconds.)
-
khenggelJust updated to 7.0.15 and like you said the issue was gone. Thank you for this support and the awesome work in general!