Release 2.5.30
Issues fixed
Export results are no longer lost when a database deadlock interrupts an item's save
Previously, when SQL Server chose an export's save of an item as a deadlock victim, the item's export result could be lost while the job still finished green and counted the item as exported. The item then showed as a Difference in the Source entities statistics, and the job log said nothing.
Keys are now created before the item is saved, which removes the deadlock that was most common in exports. A deadlock that still interrupts an item's save, or a save that fails to commit, now fails that item with an error, so it can no longer pass as exported.