Transactions are Database 101! We are finally getting new hardware to be able to run Pro and have started serious testing and just ran into this issue. The majority of our project databases don't need to be versioned and requiring that overhead to ensure we can undo an edit is ridiculous. Our data is unversioned because we don't have long edit transactions, parcel fabrics, or network topologies. What we do have is integration into larger systems and we don't want the hassle of reconcile/post or move to base processes. I still have to remind our developers to use the archive views instead of base tables and that is much more straightforward. We can live with UI changes and all the random slowness of Pro, but live editing of data with no undo is a show stopper.
... View more
Syncing has been an ordeal for us as well. We have found that 500 errors result from bad geometries. We had analysts creating slivers while clipping polygons in ArcMap. Deleting the slivers got the sync back on track. Our data isn't versioned, but you might try reconciling and posting all versions and check geometries. We have gotten just about every sync error imaginable and had ESRI pretty stumped. Moving our SDE database and AGS to 10.3.1, upgrading our app to 10.2.6 and throwing more RAM at our web server seems to have solved most of our 400 errors. There were no specific bug fixes that applied to us, but everything has run much smoother in the last month.
... View more