Icloud Uploading Stuck. Does anyone know why it actually does this? The attached image is what's currently displayed if I click on the wheel in Finder. Is it related to 'bird' and if so how? 



But does anyone know what causes this to happen?

OK. Thanks to another post, I'm on the trail of the culprits.

robert@zeus brctl-dump % brctl monitor com.apple.CloudDocs|grep % 
 o /com~apple~CloudDocs/Downloads/badaboombb_ot/fontinfo.txt ↑ 2 KB (1834) 95.0% 
 o /com~apple~CloudDocs/Downloads/backissuesbb_ot/fontinfo.txt ↑ 2 KB (1834) 95.0% 
 o /com~apple~CloudDocs/Downloads/Afans Live Filters - for Designer 1.6.zip ↑ 92 KB (91525) 95.0% 


And so on for a maybe hundred files in my case. All files show the little UP arrow, indicting that uploading is still taking place, and the percentage left at the end of the file info. All of them 95%
SO it seems to be getting stuck at 95%? 
Also, some of the files listed no longer exist. I've long since deleted them, yet here they are still in the upload list. What to do.

I found this useful info in another post here. View amount of time left when uploading files to iCloud

======== Progress of sorts ========

In all this - Photos is syncing perfectly. Anything from any of my devices, iPhone and iPad is syncing perfectly. It's just this Mac that seems to be stuck.

Doing a 'log show | grep Cloud streams a LOT of information about what's happening. And this looks interesting, and there is a lot of it repeating. Does this indicate something is Stuck and throttling iCloud?

2020-01-22 13:18:20.328917+0000 0x459b     Error       0x807e               469    14   bird: (CloudDocsDaemon) [com.apple.clouddocs:default] [ERROR] Failed to remove sync root bit [22: Invalid argument]
2020-01-22 13:18:20.329095+0000 0x459b     Error       0x807f               469    14   bird: (CloudDocsDaemon) [com.apple.clouddocs:default] [ERROR] Failed to remove sync root bit [22: Invalid argument]
2020-01-22 13:18:20.329174+0000 0x459b     Error       0xbc20               469    14   bird: (CloudDocsDaemon) [com.apple.clouddocs:default] [ERROR] renameat(-1, '&lt;private&gt;', 21, '&lt;private&gt;', 4) failed after trying to fix permissions [17: File exists]
2020-01-22 13:18:20.329313+0000 0x459b     Error       0xbc21               469    14   bird: (CloudDocsDaemon) [com.apple.clouddocs:default] [ERROR] -[BRCStageRegistry moveFromStage:toPath:fileName:error:]: (passed to caller) error: Error Domain=NSPOSIXErrorDomain Code=17 UserInfo={NSDescription=&lt;private&gt;}
2020-01-22 13:18:20.329422+0000 0x459b     Fault       0xbc22               469    14   bird: (CloudDocsDaemon) [com.apple.clouddocs:default] [CRIT] UNREACHABLE: Failed to move from fault stage to live Error Domain=NSPOSIXErrorDomain Code=17 UserInfo={NSDescription=&lt;private&gt;}
First, have you tried the suggestions in this thread: https://discussions.apple.com/thread/251061918

I have tried all the things that Apple support pages suggest, such as force-quitting Finder, rebooting, rebooting into Safe Mode, all to no avail.

If those don't work, I suggest you contact Apple Support directly on this one. I am working with them on what I believe is an identical issue of iCloud files not syncing from my Mac (macOS Catalina) to iCloud since the last few days. 

Go to https://support.apple.com/icloud and scroll to the bottom and click on the "Get support" link and choose "Update, Backup, and Restore". 

I have spent perhaps 3 hours with 3 different support people as the issue gets escalated to the support engineers. 

I don't know about you, but some files do sync up and back just fine, like those associated in iCloud Drive with certain applications (eg, Drafts, MindNode). I can create a text file at the top level of iCloud Drive and it syncs. But not for folder that I create manually. 

I have gone through a macOS Catalina re-install (via Recovery Mode) and that did not solve my problem. I am now awaiting the support engineers to review diagnostics information from my computer. When I have a definitive answer, I will report back on what hopefully solves my issue. 

I had wanted to comment on your post, rather than answer it, but I don't have sufficient reputation points to do that. 

Cheers, David