I was on that journey as well. Dropbox sync just had issues that never got resolved. I switched to iCloud. Word of warning, iCloud so far had no issues but is utterly unreliable as well.
Syncs take up to 24 hours to show up on my devices. I switched note-taking to Bear.app now (also icloud) as the sync is instant.
I’m afraid DT feels less stable these days. I have experienced a number of “Failed database verification” messages and Orphaned files PLUS the constand Dropbox errors. This does not happen with other apps which use Dropbox such as 1Writer, Drafts, Obsidian etc etc
This is not an apples-to-apples comparison.
Also, have you started a support ticket as you’re reporting abnormal behavior?
Nobody cares if it is apples-to-apples when DT doesn’t work? Which is why I am now forced to use Bear (or some other note-taking app with a more reliable sync)?
Thanks for your support. With database maintenance the issues have been resolved. A lesson for me to establish a regular routine.
You’re welcome 
I‘m still having the problem with Dropbox sync. Anybody else?
Are you actually having sync problems, i.e., things not syncing?
I’m still getting the error message – but doesn’t appear to be causing a problem with the sync itself.
I’m experiencing this same error message many times daily. Since te Sync seems though to work properly, I wouldn’t complaint, except that if DT is running in full screen mode, the error window will show up on another virtual screen when switching to DT. And it just fills up journal with error messages which don’t seem to be relevant. Would appreciate an option to filter these error messages
It seems to sync without mistakes but produces lots of error messages such as “Timeout. (NSURLErrorDomain -1001”, “Überprüfung fehlgeschlagen”, or “dropbox.com 429”.
I must say that this makes me very nervous and I had not seen it before in the last years when I used Dropbox for syncing (and saving) my DT databases.
Dropbox (or iCloud, Google Drive, etc.) isn’t a static service that never changes over time so of course they make changes, not only to the service but also to their policies.
And as always, we have no control over the changes they make (and they do not always publicly inform third-party developers of changes).
I know. I need the most stable backup and sync system and for a long time it seemed that Dropbox is the first choice. Are there any alternatives that are more reliable?
Noting that sync is not a backup, there is no 100% bullet-proof option. Every remote sync option has inherent weaknesses (discussed many time on these forums). And given the natural variability in equipment and environment, no provider can guarantee you such a thing.
The closest you’d get would be doing local syncs on your own network, which still can’t guarantee 100%, but are technologically closer to making that possible.
1 Like
I had the problem when I had Automatic Sync turned on. Once I changed to manual the problem disappeared.
Very strange. Did you switch back to automatic?
Yes this would work as sync wouldn’t be checking automatically at intervals.
I also get the same NSURLErrorDomain -1001 error but I’m running a webdav sync store, not Dropbox or iCloud. But what’s very weird is that I have 5 databases, 4 of which sync with no problem with the same webdav server. But the 5th always produces the error during sync.
I verified the original database, and verified and cleaned the database in the sync store. I also checked the permissions in the sync store and changed various timeout settings in my apache server (on the sync store machine). Nothing helps: 4 databases sync but 1 refuses to.
And more weirdness:
All 5 of the databases produce the following apache error message, regardless of whether the sync was successful or not:
[dav:error] [pid xxxx] (70008)Partial results are valid but processing is incomplete: [followed by ip & database info] [400, #0]
This has nothing to do with Dropbox or iCloud. It’s just an ubuntu server I use for sync store. By the way, I have another similarly configured ubuntu machine I also use, and it syncs everything just fine.
Any suggestions what else I might try?
The 1001 warning being reported in this case is not unusual or unexpected. It’s still a remote sync location and the warning is regarding the responses of the remote server.
Are you accessing the WebDAV server from outside your network?
Thanks for feedback. I understand what you say and we all know IT is not a static world with changes in all parts of used S/W regularly. Though we are paying for S/W (sometimes big amounts) and expect some service for it. I can easily live with that error message if it’s not preventing proper sync. What I’m complaining about is that it logs errors which are not relevant and there shall be a way to avoid it and thus not add many clicks a day for nothing…