Point Layers Failing to Sync Across a Distributed Collaboration

[MikeEtterGIS]

I am supporting a workflow where we are sharing content from ArcGIS Enterprise to AGOL via a distributed collaboration and I'm seeing strange behavior where we can share line and polygon layers but not point layers.

Our data is in a SQL Server Enterprise Geodatabase. It is NOT versioned so we have archiving, editor tracking, and global IDs enabled.

We are serving up feature services with editing disabled, sync enabled, and export enabled. Version Creation is set to None. 

Enterprise is at version 11.3 and we are sending content to AGOL as copies (sending references didn't work at all).

I'd love to hear what I'm missing here since our line and polygon layers with the same configuration are working fine.

[AmyRoust]

Do you get any error messages when the point layer fails to copy? Usually the messages are pretty worthless, but every now and then you get something helpful.

I've fought the distributed collaboration with almost the same setup you described. Another thing you can check is if your point layer has any fields hidden in the attribute table in your Pro project. I had layers fail to sync when certain fields were hidden (globalID, editor tracking fields, shape, OID). 

[JohnLivengood]

I've also had multiple layers fail to sync on 11.3 to AGOL.  Deleting the layers on AGOL and manually running a sync usually fixed it but...11.3 has been different.  Esri has been releasing various patches intended to fix distributed collaborations, as recent as a week or two ago.  I have seen another one a couple months ago.  These collaborations had been so unstable I just deleted everything and added the rest endpoints manually to AGOL.  I will revisit eventually to see if these patches resolved the issues.