i have a problem with a WebDAV sync store. The log entry (in the Cloudy directory) shows “No downloadable contents for X items found.”.
For example, my indexed files are no longer moved and so on. However, the database will obviously be changed, so with the next sync attempt errors appear and the database must be repaired. But this does not work because the files can’t be downloaded (manually).
Sync does not work anymore with indexed items.
Is there a way to reset this status or do i have to create the sync store from scratch?
BTW: It would be better, if DT won’t sync the database if there is such an issue.
The way I see it is that DT “syncs” the database but then doesn’t load or move the files because other content that was previously synced isn’t available and blocks the new correct sync.
Maybe this answer irritates. More specifically: I can fix the errors by hand by simply copying the missing files into the indexed directories in the Finder. Nevertheless, the database can not be synchronized even “Verify & Repair” doesn’t show any errors. But that only affects the WebDAV Sync Store. Via Bonjour syncing is possible.
If I understood correctly, you do not control the WebDAV server, but it’s Cloudy that is responsible for it?
The 8 files you mentioned: Are they always the same? Anything special like size or extended attributes?
The affected files are from October 2021 and earlier. I hadn’t any sync issue until last week. Maybe with the last update to DT 3.8.2 the sync engine stops syncing if pending downloads are in the “cache”…
I continue to have repetitive sync problems with databases with indexed data (see above). I would like to be sure to reset the entire sync. Which files should I delete in the Cloudy Folder to perform a complete reset (maybe after first remove the sync locations in DEVONthink Sync settings)?
Which files should I delete in the Cloudy Folder to perform a complete reset (maybe after first remove the sync locations in DEVONthink Sync settings)?
Not yet. I will first delete the entire sync store and reconfigure it on all clients to rule out an error in the sync store. If the error still occurs, I will open a support ticket… Thanks!
