The issue is a result of how the branch versioning metadata is maintained during save edits, reconcile and post. During these operations, branch versioning metadata may be removed from the geodatabase. When the branch version metadata is incorrectly removed, features may not correctly participate in future operations such as reconcile, post and delete version, resulting in inconsistent data. This issue occurred under race conditions where competing requests caused branch versioning metadata to be incorrectly removed for valid features.
Operations executing against incorrect branch versioning metadata could lead to:
- Branch versioned data referencing a version which has since been deleted, and,
