I don't have a perfect answer and neither did ESRI, but I'll give you our best explication. If the the user makes an edit then posts to the QC and stops editing, then goes back to the same feature and edits it again, stops and saves edits. That evening our nightly script runs that post and reconciles all versions to the QC then to the default, for some reason that causes the the database to throw a conflict. I know this isn't a perfect answer and it doesn't really make sense, seeing as how the delta tables should be keeping track of the edits and edit sessions, but this is the best reason that we have come up with. We haven't had the problem in a while, it just went away. We have told all of our editors to:
- complete the whole process if they are going to post and reconcile periodically throughout the day.
- If possible try and refrain from posting and reconciling during the day, simple save you edits and stop editing. The process runs every night and people will see the changes you made the next day
- Don't leave an edit session open when you leave for the day.
These are the types of practices that we have implemented to mitigate this problem from reoccurring.