@SHust we do have these happen from time to time & it happens when server load is super high - in the meantime you can undelete the contact, re-add the email & re-merge them to fix the specific contact (let me know if you want to run through it on a call)

We could probably do a patch to wrap each dedupe in a transaction - it would need upstreaming so maybe a phab on the feature board to do that

@Eileenmcnaughton would you like me to create the phab?

@SHust It looks like the 'wrap each dedupe in a transaction' isn't quite what we need to do here. Eileen has suggested instead we run a regular job to alert us to these problems so we can know how frequent they are and fix them.

In T326583#8924670, @Ejegg wrote:

@SHust It looks like the 'wrap each dedupe in a transaction' isn't quite what we need to do here. Eileen has suggested instead we run a regular job to alert us to these problems so we can know how frequent they are and fix them.

Did Eileen say how the proposed new job should work? Possibly something along the lines of checking recent merges and confirming the closed contact's donations are present on the surviving record.

@jgleeson I believe this issue has been resolved!