Comment 13 for bug 1836754

The error message that's being provided basically says exactly what's supposed to happen here: retry the operation, looks like Matt had a solution along those lines and Eric had a refinement that was less complicated but more aggressive. Since the instance is supposed to be gone, I would think the aggressive form is probably fine.

If there's been an uptick of the conflict happening that does suggest that transaction has delayed visibility of change a bit. Am I right in recalling that these are instances that are being destroyed very soon after creation?