This occurred in a one-off scenario where two conflicting download processes were coincidentally ran at the same time, and attempted to create multiple transactions for the same gift.
There are a couple of options to handle this scenario:
- Manually enter the gift based on the transaction XML from the Failed Transactions tab, and delete the failed transaction.
- A copy of data could be pulled to evaluate the data and develop a scenario-specific script to correct. This would take significantly longer to create and test, than would the first option.