Hi @MDemosWMF thanks for raising this - please go ahead and delete the duplicates, flagging for @Eileenmcnaughton to have a look.

Thanks @Anil1956 !

@MDemosWMF - we did used to have strict rules in place to prevent duplication & we relaxed them over time due to all the exceptions - that is probably what has changed

"it gave me the 'database deadlock, return to home' notice, so I submitted the batch again" - did that happen when you clicked submit?

@Eileenmcnaughton Yep, after I clicked submit it does the twirl triangle like it's processing and then goes to another screen that says 'database deadlock, return to home.'

Maybe it's finding a middle ground - is there a way for it to show which gifts have gone in before the DB deadlock hit? maybe on that DB deadlock screen? Right now we would have to create a search to try and see if anything went through and that can take time.

@MDemosWMF where are we at with this one - do we still need to do anything?

@BJordan-WMF Can you please weigh in on how the batch data entry imports have been going and if you notice these duplicates after import still occurring?

@MDemosWMF I do believe this is still a presenting issue. I have been splitting large batches into two parts to avoid deadlocks, but I had one last week that resulted in duplicates.

I think the issue here is not knowing what gifts made it into Civi without doing a separate search after hitting the deadlock - could it operate like the mapping imports where it shows which gifts imported directly on that screen? More visibility into what has occurred with the import on the deadlock screen would be helpful.

@MDemosWMF Ok to close this one since we've switched to the new imports?

@Lars Yes, I think this should be resolved - we will let you know if it pops up again!