Answer
This happens when the queue is trying to insert site statistics that already exist at the satellite — check for duplicate messages in the affected queue (a finished application message sharing the same sender message ID as the one that's now failing). If duplicates are present, enable the 'IGNORE_DUPLICATES' functional property in Data Synchronization configuration — this is a dedicated property built specifically to handle this class of duplicate-message replication failure.