Skip to content

This error is raised when MoveData processes a refund but cannot find the original donation Opportunity it needs to update.

Error message#

You may see this error in your execution log:

Cannot Refund due to missing original Donation.

For help finding this error, see Reading and understanding error messages.

What causes this error#

When a refund notification arrives, MoveData looks up the original donation Opportunity in Salesforce using its platform key (the movedata__Platform_Key__c field on the Opportunity). When that Opportunity isn't present, the refund pipeline halts with the exception you've seen — this is the validation step working as designed rather than a bug.

A couple of common reasons the original Opportunity may not be there:

  • The original donation notification never landed (for example, it failed earlier, was skipped, or the donation pre-dated when the integration started polling).
  • The Opportunity exists but its movedata__Platform_Key__c value doesn't match the one the refund is looking for (for example, it was created manually or via a historical import).

How to fix it#

The fix depends on which of the two causes above applies.

If the original donation notification never landed#

  1. Open the Notifications tab in the MoveData app and search for the original donation by platform reference, donor name, or date.
  2. If you find a Failed notification for the original donation, resolve the underlying error and reprocess it first. See How to reprocess failed notifications.
  3. Once the original donation has succeeded and the Opportunity exists in Salesforce, reprocess the refund notification.

Note

MoveData retains notifications on a 90-day rolling basis. After 90 days, notification data is automatically deleted, so notifications for older donations will no longer appear in the Notifications tab even if they were processed successfully at the time. See Understanding notifications for details.

If the Opportunity exists but the platform key doesn't match#

  1. In Salesforce, find the Opportunity that corresponds to the original donation.
  2. Compare its movedata__Platform_Key__c value with the platform key referenced in the refund notification's execution log.
  3. If the values differ, update the Opportunity's movedata__Platform_Key__c to match the value from the refund, then reprocess the refund notification.

Warning

Only change movedata__Platform_Key__c when you are certain you have identified the correct original donation. The platform key is what MoveData uses for duplicate matching, so an incorrect value can cause future notifications to create duplicates or update the wrong record. See How the donation pipeline works for context.

If you can't find the original donation at all#

If the original donation pre-dates your MoveData integration, or was never recorded in Salesforce by any route, there is no Opportunity for the refund to update. In that case, handle the refund manually:

  1. In Salesforce, create or locate the Opportunity that represents the original donation.
  2. Adjust the Opportunity to reflect the refund (for example, change the Stage or Amount).
  3. Mark the failed refund notification as resolved in the MoveData app.
Ask MoveData AI
Ask about setup, configuration, or troubleshooting
How can I help you with MoveData today?