We have been using Collector for about 18 months but have experienced a new error whilst attempting to sync offline edits.
Sync Error: Operation rolled back.
Once this error occurs, I have deleted one feature at a time and attempted to sync each time. At some point, I am able to sync successfully. The strange thing is that once this point is reached, I can re add the same feature type with the same attributes and I can successfully sync.
7 edits can't sync, 'Operation rolled back'. Remove 1 feature.
6 edits can't sync, 'Operation rolled back'. Remove 1 feature.
5 edits can't sync, 'Operation rolled back'. Remove 1 feature.
4 edits CAN sync, Add last feature that was removed. Success. Can sync.
Add 7 features. Sync Successful.
Each feature type can be synced successfully individually. Many can be synced successfully collectively.
Occurs on three different iPad Air 2's, using two different AGOL logins. Collector version 10.4.1. Latest iOS.
The project itself is fairly complicated with one to many relationships. Considering successful syncs, this shouldn't be an issue.
Operation Rolled Back? What does it mean?
William - I don't have a definition of what "operation rollback" means but in reviewing Support Services incidents with similar error messages, I found a circumstance where it does happen.
Hope this helps!