Yes this began happening to me as well on Saturday night for all of my 'by-reference' collaborations, where agol is our host and portal at 11.3 is the guest that sends content to agol 'by-reference'. We've been dealing with TS Debby and so haven't had a chance to dig into this yet
I am not running any 'as-copies' collaborations, so for us, the cluster should not matter, but we are on services3.
Yes, as before, after a collaboration fail, the replication packages are left behind. In my case, I have 8 thus far.
In the past, I too would remove the packages and allow the replications to run again by schedule - but this time this is not working, they are failing again.
My only option now is to delete and recreate the collaborations, but that does not come without risk - the primary one being if the new collaboration does not work, I will have to remove the reference layers from the agol group and try and have the collaboration re-send the portal hosted layer references. And although the layer ids should stay the same, you never know how.
I would tag you guys but the '@' doesn't seem to be working at the moment either.
