Sync Failed Error: Unable to synchronize replica. Sync replica Internal error.

JustinH · ‎05-08-2024

Hi Everyone-

I continue to have an annoying Sync error in my field maps. It seems like this was an error in Collector, but I am unable to find a solution to get rid of this sync error.

In offline mode, every time I hit sync, I get the error "Unable to synchronize replica. Sync replica internal error." But the edits that are made still push to the source.

So, there is no issue with what field users need, but it happens to tell the field user that everything is failing... I would love to eliminate this error so users have a smoother UX.

Thanks for the help in advance.

TravisSizemore · ‎05-08-2024

Justin,

I know this doesn't help, but we have been dealing with this error for years with one of our web maps. It happened in Collector and now in Field Maps. In our case, we have a Join layer present in the map that I think causes the error. The Join layer isn't editable, and is just for reference, but Field Maps/Collector doesn't like syncing with that layer in the map. However, as you mentioned, all the data does sync properly regardless.

Travis

JamieChelberg · ‎08-23-2024

Travis and Justin,

I have been having a similar issue. On FieldMaps when the crews get back to the office and try to sync the offline map (which they download prior to leaving and no schema changes are made while they are out), we get the error "Unable to synchronize replica errors" and the log shows Fri Aug 23 16:25:18 PDT 2024 : [SYNC] - [914dea11e1eb4ef2887f849747370a81] - Error syncing map: null
Fri Aug 23 16:25:18 PDT 2024 : [SYNC] - [914dea11e1eb4ef2887f849747370a81] - Layer: Microhabitat Use Error: Service error code 500 : Unable to synchronize replica.
Details:
Sync replica internal error - 198ca263-2613-4a4e-accf-f458c4199009. Which tells me that the layer is the issue. However, I cannot get it to go away. I have removed all the calculations and conditional formatting and it still does it...I am trying to not have to reload the layer because it is quite a few attributes that had to be formatted in the form...If a solid fix comes, let me know.