Given the difficulties you had, I wouldn’t want to impose on you.
Since it’s synced now, you could just keep a eye on the performance and if the domain errors recur often in general use.
Thanks!
Eh, what the hell. I’ll take one for the team if it could help someone else. Won’t be until tomorrow at the earliest though.
As you wish and it would be very appreciated.
Before you do, coudl you go into the Help > Documenation > Appendix > Hidden Preferences and click the On link under SyncDebugLog? This will do deeper logging that may bear some fruit.
It was just over 9 GB - it is uploaded now but I can’t access the machine I sent it from as my remote link has fallen now. Going to the office soon to check out what’s happened. Will let you know number of records then. I am doing a 20GB one now.
Fwiw I’m finding the errors seem to somehow grow fewer the longer the sync runs for.
I noticed the DTTG 3.0.1 Update this morning. That was fast.
However, the annotations folder issue does not seem to be fixed, more specifically:
- added an annotation to an existing item in DT on macOS
- DT automatically creates an item in the DB’s Annotations folder
- synched to iOS
- the (Annotation) item is in the root of the DB in DTTG (and not in the Annotations folder)
Presumably not as intended?
If you need additional information, let me know.
You might need to move something manually into the Annotations folder to trigger a change. Then sync. The Annotations folder on the iOS device should change its icon into one with a star on it and move up to the Specials section. Now it should all work.
Hmm, did 2 things:
- manually moved the Annotations item from the wrong place (DB’s root) into the Annotations folder
- modified an existing Annotation on macOS which resulted in the Annotation file in the wrong place again (was in Annotations folder yesterday where I had moved it manually, now it’s in the root again)
The Annotations folder looks like a normal folder, it neither has a star nor is it in the Special section.
I am having a pretty smooth run of it now. One database to go which is on my remote machine, have to go there to sync it. It’s very encouraging, but also strange, that the errors seem to fade into the background as you go (and I have been doing the syncs one by one so it’s not that they were concurrent and fell off along the way). In any case, I agree things seem to be better than legacy iCloud sync once you get the stuff up there.
1 Like
Please try to rename the Annotations group, or mark it with a flag. Then sync. Does that change the group’s appearance in DEVONthink To Go?
Okay, I’ve posted three different entries on ticket #336060.
OK, very strange behavior:
- When I change the Annotations group on iOS, those change are reflected on macOS (both Flagged and Renaming)
- When I change the Annotations group on macOS, none of those changes is reflected on iOS
It’s like a one-way street.
Annotations (or whatever its name after the change) stays a normal group. Files in the Annotations group are moved to the DB’s root whenever a change on iOS (or macOS?) triggers a sync of that group.
Got it. Thanks
PS: You can disable the SyncDebugLog now.
1 Like
Then my suggestion would be: Create a new Annotations 2 (or whatever) group in DEVONthink for Mac. Move all annotations there for a moment. Delete the real, special Annotations group. Empty the trash (important). Sync. Now the wrong Annotations group should be gone.
Then create a new annotation on some document. It should create the Annotations group anew. Sync. Now you should get a proper Annotations group with bells and whistles. New annotations should end up in the correct group. Move the annotations you saved to the temporary group back.
Well, that worked 
Thank you!
Thanks for the reminder about the log.
No problem.
I have the same issue with cloudkit, 99Gb database that only has indexed files. I have a fiber connection so I’m getting 930Mb up and down. I received the issue when I sync to the Max connections of 16. I still have the issue with 1 connection. 2-3 files will upload then I get the same error “This operation has been rate limited due to an earlier error: Request failed with HTTP status code 503.” I’m not sure if it makes a difference but I’m on a wired connection when this happens.
edit Now it seems to be going steady with 1 connection. It’ll upload a about a hundred items before I get an error. I think my earlier attempts to upload using 16 connection impacted my later attempts. I have issues going above 1 connection. It looks like it’ll be going a while with 5000 items to upload. Oh well.
Sort of indicates bandwidth not the only controlling factor when using the Apple servers …
I am having this issue as well. I couldn’t get CloudKit to finish uploading any database yet. Even if set to only 1 connection, I get the same error messages as other users. Database is around 7000 items, with 500000 unique words. My bandwidth is only 50 Mbps, but uses much less (< 7 Mbps) with 1 connection. Bandwidth doesn’t seem to matter much, the errors show up after 100-200 files uploaded, no matter how slow. I disabled CloudKit and use Legacy again.
Btw, I’ve seen similar issues when I was using Keep It in the past, which also uses CloudKit. I actually switched to DEVONthink because of those issues, since they couldn’t be resolved.
1 Like
Welcome @chrk
Thanks for sharing your experience, especially regarding KeepIt.
1 Like