As of this morning, I still needed to sync my iPad. So far, it seems to be running fine. I have a lot of data to pull down, but will update here if there are issues. The last error I received on my laptop was 13 hours ago.
Cheers! I have two Macs to sync so it’s slooooow going. Haven’t even started on iOS yet.
My inbox did not appear to be synching, so I restarted DEVONthink. It appears the lack of log activity I presented in my last post was due to some kind of issue that the restart fixed.
| Time | File/Action | Info |
|---|---|---|
| 08:57:59 | Request failed with http status code 503 | CKErrorDomain 6 |
| 08:58:45 | Request failed with http status code 503 | CKErrorDomain 6 |
| 08:59:52 | Request failed with http status code 503 | CKErrorDomain 6 |
| 09:00:06 | Request failed with http status code 503 | CKErrorDomain 6 |
| 09:00:15 | Request failed with http status code 503 | CKErrorDomain 6 |
| 09:00:19 | Request failed with http status code 503 | CKErrorDomain 6 |
| 09:00:53 | Request failed with http status code 503 | CKErrorDomain 6 |
| 09:01:04 | Request failed with http status code 503 | CKErrorDomain 6 |
| 09:01:20 | Request failed with http status code 503 | CKErrorDomain 6 |
I realize this error means the site is not available at the moment, but I am synching on my iPad while I get these errors on my Mac.
To be honest I’m finding it terrible to upload to iCloud. I haven’t even started on my large databases. Every few minutes my laptop redownloads an unchanged database instead of uploading the one I want to upload. 
Been at it all day… Running one machine at a time, 1 connection. Breaks down every minute.
1 Like
Yeah, I’m having nothing but trouble out of CloudKit. If there is something you need me to test, I’d be happy to do it, but it’s back to Legacy until you need me to test.
It keeps resynching unchanged databases that were synched 10 mins ago instead of uploading the one I want to synch.
1 Like
You’re reporting issues we can’t reproduce at will here. In fact, most people are experiencing very positive results with CloudKit.
Disable the other databases from syncing, then quit and relaunch DEVONthink. When the sync of the desired database is done, re-enable the others.
My databases finished uploading overnight. I am still seeing the 503 errors, but much less frequently.
Downloading from CloudKit on my other Mac, iPad, and iPhone was SO FAST. I was able to do them all simultaneously. And they all finished in under an hour. My phone got hot it was writing so fast.
Thanks for responding. I’m sure it will be fine in the end. I’m encouraged you’ve had good feedback, I’d expect it to be better than legacy iCloud once I have it all up there. I’ve tried disabling databases selectively but then they redownload and I have to wait to upload the next. Right now I have one machine chugging away at my fourth largest database, hopefully will be done before I go to sleep so I can run the next. Sync operation is definitely smoothing out anyway, but still slow going. OTOH I have a lot of data so it comes with the territory.
If you are getting very positive results from most of your customers, with respect to CloudKit, I wonder what makes us unique?
1 Like
I give up… changed back to iCloud (Legacy). CloudKit does not sync well. Error codes every 3 minutes. This ist not okay. It is not working.
A otherwise happy Devonthink customer for many years…
Please post an update in the Devonthink Block when the new Sync mechanism finally works.
Same here:
Incessant CKErrorDomain 7’s for me.
Note states “This operation has been rate limited due to an earlier error: Request failed with HTTP status code 503”
Back to “Old School”
Update: after watching closely - the sync seems to shut off at 100 documents - this is with any number of connections I have set.
So 1,2,3,4…100 - slam
wait
repeat
It will eventually sync with all of these errors, it just takes time as it will keep syncing in chunks before hitting an apple limit. Once it does do the first sync, everything is amazing.
2 Likes
My issue at the moment is that, after a while, DEVONthink just stops attempting to synch (and I’ve waited for hours to see if it makes another attempt) and won’t try again until I completely quit DEVONthink and restart it. So, at least in my case, it won’t complete on it’s own. Things I’ve tried so far:
- Changing the Max Connections setting to everything between 1 and 16
- Completely removing all DEVONthink sync information from iCloud and starting over with CloudKit (3 times so far)
- Running Verify & Repair on all databases
- Removing DEVONthink To Go from all iOS devices (an iPad and iPhone) while waiting for the Mac (MacBook Pro M1) to complete the initial sync
- Attempting to sync one database at a time
- Attempting to enable sync for all of the databases and just letting it run
MacBook Pro Information:
- MacBook Pro (13-inch, M1, 2020)
- Chip Apple M1
- Memory 16GB
- Local Disk: 730.44 GB available of 994.66 GB
- iCloud Storage: 1.33 TB available of 2 TB
2 Likes
While I can’t speak to others’ experiences, I’m on my second day using CloudKit sync and I’m very happy with it. The performance of sync for individual changes is amazing and well worth the conversion effort.
The CKErrorDomain 6 & 7 errors are temporary and related to Apple’s rate limits. I saw plenty of them during my initial sync of my data from my Mac. Since then, I have had none of those errors.
I am using the default configuration on my Mac and two iOS devices. On the Mac:
- Sync: Automatic (this is key! with this set, DTPO recovers from the rate limit error after about 2 1/2 minutes and then continues on)
- Max connections: 16
- Conflicts: Use latest
On my iOS devices, I did kill and restart DTTG when it appeared to be stuck the first time or two. Then I just left it alone and noted that it also recovered from the rate limit errors and continued.
I held off on syncing my iPad until this morning. I found that the rate limit of the initial upload had expired and sync to iOS ran along without error. I was able to sync a large database (>100,000 items) this morning to iOS in a couple of hours where this used to take overnight with the Legacy iCloud sync method.
3 Likes
For my experience after having the same errors as all of you I let all night long running the sync on my Mac and this morning all was correctly synced (I had put the sync connection number at 1 following some advices here).
I ran then my sync on my iPad and it worked well without errors and by far more quicker than with my previous sync on Dropbox.
I just changed the parameters following ddmckay I’ll see if I encounter issues when DTPO will resync next time.
2 Likes
How large is this database and how many records?
That’s what we’re trying to gather info to determine. None of us in-house can reproduce an issue at will, which is actually logical since the error is from Apple’s servers.
Did you start a support ticket via Help > Report Bug while holding the Option key?
I have not. I have everything synch’d now, and the updates seem to be working. Do you want me to delete everything and start over to see if it provides any information?