Duplicate update numbers in sys_audit table for concurrent record updatesIssue When two users update the same record at the same time, both updates are added to the sys_audit table with the same value in the update number field. This article explains why this occurs and how to confirm the behavior. Release All supported releases Cause Both update transactions are isolated from one another. Because the updates happen concurrently, each transaction reads the same previous sys_mod_count value from the target record and uses it as the update number. Neither transaction sees the other's change before writing to the sys_audit table, so both rows record the same update number value. Resolution This is expected behavior from an audit perspective. During concurrent updates, ServiceNow reads the current sys_mod_count value of the target record at the start of each transaction. Because both transactions start before either has committed, both read the same sys_mod_count value. That value is then written as the update number for each audit row, producing two rows in sys_audit with the same update number.