CloudKit syncing is great, but on my main machine, it just stops syncing after a while (just now, it hadn’t synced in 4 days).
If I go into the Settings, the spinning indicator just spins and never moves to another database.
If I choose Quit (or ⌘-Q), the task progress box bottom left says Completing Synchronisation…, but it doesn’t ever progress past one of the databases.
If I choose Quit (or ⌘-Q) again, DTP immediately quits, I re-open, check Sync settings, and the databases all successfully sync in turn. There’s nothing listed in the Log after a successfuil sync.
This has been happening through various DTP4 revisions.
On my secondary machine, syncing just works.
They are both on Sequoia, both on latest DTP4, one is an Intel machine, one is an ARM machine.
Have you run verify and repair on the affected database in all locations, and then verified the sync store? It’s the first step in troubleshooting sync in the manual and usually fixes the problem. (Or finds a new one you didn’t know about…)
Yes, when a DB stops synching, normally it is a somewhat corruption of it. It happens to me almost monthly with my tiny DB dedicated to handle some RSS feeds.
In the past I have experienced downloads getting “stuck” and have successfully used Howard Oakley’s freeware Cirrus to “unstick” them. It might be worth a try: