Reading and understanding error messages
Dealing with errors can be frustrating, but MoveData gives you the information you need to work out what happened. This article walks you through where to find errors, how to read them, and what to do next.
Before you begin#
- You need access to the MoveData app in Salesforce.
- You should be comfortable navigating Salesforce tabs and list views.
- Familiarity with your integration's basic data flow is helpful but not required.
- For background on key terms used here, see Key Concepts & Glossary.
Understanding notification statuses#
Every notification in MoveData has a status that tells you whether processing succeeded. Before looking at error messages, it helps to know what each status means.
| Status | What It Means |
|---|---|
| Success | MoveData processed the notification without errors. |
| Failed | Processing hit an error and stopped. This needs your attention. |
| Skipped | MoveData did not process this notification on purpose — for example, because it was a duplicate or your rules filtered it out. |
| Processing / Queued | MoveData is working on this notification or it is waiting its turn. |
A Failed status is your signal that something needs investigation. A Skipped status is usually expected behaviour, not an error.
Finding errors in MoveData#
Step 1: Open the MoveData app#
Click the App Launcher (the nine-dot grid icon in the top-left corner of Salesforce). Type "MoveData" into the search bar and select MoveData.
Step 2: Navigate to the Notifications tab#
Click the Notifications tab in the MoveData navigation bar. This shows all notifications from your connected platforms.
Step 3: Filter for failed notifications#
Select the Failed Notifications list view from the drop-down at the top of the list. This filters out successful and skipped notifications so you can focus on errors.
You can also use platform-specific views (such as Raisely Notifications or JustGiving Notifications) to narrow your search to a particular source.
Step 4: Open a failed notification#
Click on any notification in the list to open its detail page.
Success
If you have error email alerts turned on, MoveData sends you an email when a notification fails. You can configure this in Settings > General.
Anatomy of an error message#
Error messages in MoveData follow a consistent structure. Knowing each part helps you diagnose problems faster.
The execution log#
The detailed error information lives in the Execution tab on the notification detail page. Click this tab to see a time-ordered log of every step MoveData took while processing the notification.
For a full guide on reading the execution log, including the Variable Inspector and log settings, see Viewing execution logs.
What to look for#
When reading an execution log for a failed notification, scan from top to bottom. The log runs in time order, so the error appears where processing stopped. Look for error-level entries — these stand out from the routine informational entries above them.
The Group column tells you the phase. The Message column tells you the problem. The Detail column tells you the specifics.
Error categories#
Most errors you encounter in MoveData fall into one of these categories.
Validation errors#
Salesforce rejected the data because it did not meet a validation rule, required field, or picklist (drop-down list) restriction. These are the most common errors.
Examples: A required field had no value. A state or country value did not match Salesforce's picklist. A custom validation rule on the Contact object blocked the save.
Lookup failures#
MoveData could not find a matching record in Salesforce.
Examples: No campaign found with the given identifier. A required lookup field could not be resolved because the target record does not exist in Salesforce.
Permission errors#
The MoveData Authorised User does not have permission to create or update the target record or field in Salesforce.
Examples: Field-level security (which controls who can read or edit specific fields) prevents writing to a custom field. The authorised user does not have "Edit" access on a particular object.
Platform errors#
The source platform returned unexpected data, or the connection to the source platform hit a problem.
Examples: A required field from the source platform was empty. The response from the platform's API (the system MoveData uses to exchange data) arrived in an unexpected format.
API limit errors#
Salesforce governor limits can prevent MoveData from creating or updating records when limits are exceeded. These errors occur when your org hits Salesforce's built-in processing thresholds.
Examples: "Too many SOQL queries" or "API request limit exceeded".
Connection errors#
The connection between MoveData and Salesforce or the source platform has expired, been revoked, or is temporarily unavailable. These errors usually resolve after re-authenticating or waiting for a temporary outage to clear.
Examples: "Authentication failed" or "Session expired".
Flow errors#
If your integration uses Lightning Flows (automated processes in Salesforce) for custom processing, those Flows can encounter their own faults. These appear in the execution log. See Understanding Unhandled Flow Faults for more detail.
Worked example#
Validation rule error: required custom field#
Scenario: A donation from Raisely fails during save. Your Salesforce org has a custom field called Finance Code on the Opportunity object, and a validation rule requires it to be populated.
What the execution log shows:
| Time | Group | Message | Detail |
|---|---|---|---|
| 14:32:01 | Mapping | Mapped donation fields | Amount: 50.00, Close Date: 2026-03-21 |
| 14:32:02 | Save | Error saving Opportunity | FIELD_CUSTOM_VALIDATION_EXCEPTION: Finance Code is required. |
How to interpret this: MoveData processed the donation data successfully, but when it tried to save the Opportunity, Salesforce rejected it because the Finance Code field was empty. MoveData does not set this field by default — it is a custom field specific to your organisation.
How to fix this: Create or extend a Salesforce Flow that assigns the appropriate value to the Finance Code field during the donation mapping phase. For guidance on building custom flows, see Customising MoveData. After deploying the flow, reprocess the failed notification to confirm it now succeeds.
Gathering information for support#
If you cannot resolve an error on your own, the MoveData support team is here to help. Before reaching out, gather the following information so the team can assist you faster.
What to include#
- The notification Name or Key — this lets support find the exact record quickly.
- The full error message — copy the complete text from the Detail column, not a summary or paraphrase.
- The execution log timeline — a screenshot or description of the steps leading up to the error.
- The source platform and notification type — for example, "Raisely donation" or "JustGiving fundraising page".
- Whether the error keeps happening — does it affect one notification or many? If many, do they share something in common (such as the same donor, campaign, or region)?
- What you have already tried — describe any changes you have made in Salesforce to resolve the error, and why you are still seeing it.
Warning
Avoid sharing screenshots that include personal donor data (names, email addresses, phone numbers) unless support asks for it. Use the notification Name or Key instead — MoveData support can look up the record securely.
Decision tree: what to do next#
After reading an error message, use this guide to decide your next step:
- Validation or picklist error — Check whether the data needs correcting at the source, or whether a Salesforce validation rule or picklist needs updating.
- Lookup failure (no match) — Check whether the record exists in Salesforce. If not, decide whether to create it manually or automatically.
- Lookup failure (multiple matches) — Merge or de-duplicate records in Salesforce, then reprocess.
- Permission error — Ask your Salesforce administrator to review the authorised user's permissions.
- Flow error — See Understanding Unhandled Flow Faults.
- Unsure — Gather the information described above and contact support.
Note
After resolving the underlying issue, reprocess the notification using the Reprocess button on the notification detail page. See How to Reprocess Failed Notifications for full instructions. Then check that the status changes to Success.