HP-synchronizer only can delete (during a FULL Sync) if you indicated for it to do so on your link with the ''deletion'' rule.

*The process is like this:*

Establish a record ''pair'':
During a sync, a corresponding record is created for a ''new'' record in Endpoint 1 (EP!) or 2 (EP2) (depending on your creation rules) -- this is a sync-linked EP1/EP2 pair of records

IF your rule is to DELETE a corresponding record (other end of sync-linked pair) from either EP1 or EP1, then
on the next FULL sync, the Sync-server will sense that the record was deleted and will proceed to follow the deletion rules.
If the preference was set to delete the corresponding record on the other side, it will do that.

**So, that is the ONLY way it can do a deletion** -- someone or something else has deleted your original record, and on the next FULL sync, it honored your deletion rule, and that resulted in a deletion of the corresponding record. It cannot just do deletions randomly.

This activity is ALL part of basic HP Synchronizer operation - it is following your indicated deletion rules.

Most customers using Synchronizer set this to ''Do Nothing'', then make sure their users cannot delete records from Endpoint1 or 2, and also have some status corresponding to ''Deleted'' so they can show that the records are marked for deletion or are figuratively deleted''. This way, they do not have any disasters when someone accidentally deletes a record -- and you have a preserved record all the way up to the ''deleted'' state (perhaps even with a note as to why it is that state).

Check your transaction/audit logs in your QC (EP1) and EP2 servers. If the ''automatic'' deletion happened from sync on the EP2 side, then check your QC logs for MANUAL deletions of records in the timeframe between the Full Sync that did the deletion and the previous Full sync. You will be able to tell who did the deletion.