I have been trying to work out what is happening with syncing a hosted feature layer in ArcPro 2.4.3.
SO the workflow I have been using is very simple:
So sometimes I end up running into a road block when either downloading the service or syncing the data back.
I get the error
Where do we get more information about this error?
I can't find anything its a ArcGIS Online hosted service so there are no server logs.
Is there a location in ArcPro where info about why would be saved?
currently its just keep trying holding your toungue a different way and hoping something works.
Same problem here in ArcGIS Pro 2.5.1. There are two of us working on the same hosted feature service, using the same version of Pro. Another problem we are having, when we are successfully able to sync, is we get a "Syncing offline data" box with the blue timer bar that just runs and runs and runs and never does anything. The data does sync, but Pro is frozen and we have to exit through the task manager.
I am getting the exact same error using the same method you are using but I am now running ArcGIS Pro 2.8.0. Just a blank map with a hosted feature service downloaded for offline editing. It worked last week, but now when I make edits to a related table, the sync fails with the exact same error message. Were you ever able to find a solution to this error?
I get the error also. Running ArcPro 2.8.0
Has anyone been able to find a resolution with this issue? I'm encountering it as well on ArcPro 2.7.3.
Experiencing the same issue on Pro 2.8. I am sure this worked fine before. Will try in ArcMap and see if I have the same issue. Other issue is dropping of attachments when synching to an AGO Hosted Feature Layer. Following a technical article, I went the download, append local and sync route.
Same problem here... running 2.7, and just recently switched to working on the One-drive. Did anyone have any resolutions?
This seems to still be an issue.
I have 256 sampling records that are in limbo and i cannot seem to sync this to the main feature layer.
Has there been any further progress on what can be done?
Receiving this error again in ArcPro. Has a way to track or view the error been implemented?