Files not syncing (downloading) to device B as they are "marked for upload"

edited June 19, 2024
Debug ID: D225677395

Files exist on Device A. They are synced to a webDAV server successfully and I can find the associated .zip and .prop files.

Files do not get synced to Device B (where the Debug ID is coming from). The following messages repeat for all unsynced files:

(4)(+0000011): Checking attachment file for item 1/DZJYFHHK
(3)(+0000012): File is already marked for upload

These messages appear for 45 unique items:
DKIYYHXV DZJYFHHK EMR6KC8I G64KT9WG H34JX7VG HWK544XM JGNYRBS9 KR86GIV4 LFBRP4WU MH8DHCW7 MZNUMEBH PCEPKDLR PH8H69II QHZHZ277 RCHZ6S23 SFJ4NW6Y UTCS9TV8 V52ELQ5I V8UV7LEM VSI7W55V WH8PDQF4 WZAC8XDS Y3RBLKDM Y676PFYF YEPI4PW3 ZHP6XLHI 25UNHX9X 2BX4M9B8 2FJGXXLA 2TRCVRH4 3FR6TNG5 4L4ZBE5E 4LS4MKY3 54JMNNH3 69BZMGEV 7IEAE3Z6 85AIQ5S5 9LAMJSNE AN35FHTB B5VNHGNI BFZ2S4VU BZH6SN6U C3SSFY7N D92IYJEL DA7B6LBJ

I can confirm that none of these folders on my local Zotero library folder (on device B) contain any pdf files. Even more, folder 54JMNNH3 does not exist.

I have reset the file sync history on both device A and device B previously with no success. I did previously run into an insufficient storage error, which I have since resolved (https://forums.zotero.org/discussion/115338/file-syncing-fails-using-webdav-file-exists-on-device-a-and-on-server-but-not-on-device-b).

Notably, the following folders that are attempting to get synced but are marked for upload do not have .zip or .prop files on the server likely because although they exist on device A as folders, they are empty (no records associated with them - maybe deleted?)
MH8DHCW7 PH8H69II SFJ4NW6Y VSI7W55V WH8PDQF4 2BX4M9B8 2FJGXXLA 4L4ZBE5E 69BZMGEV 7IEAE3Z6 AN35FHTB BFZ2S4VU BZH6SN6U
  • We've had one other similar report. We'll investigate — thanks for the detailed info.
  • Has there been any update on this? The same error happens for every newly added item both ways: if added on device A, the PDF does not get synced on device B and vice versa, even though the files are successfully uploaded on the server.
  • Please ignore this thread. It turned out to be a simple mis-specifications of the webdav sync settings. The first problem described might not have been due to that but I no longer have a reliable way to reproduce the issue.
Sign In or Register to comment.