What to expect after going live
Congratulations on deploying MoveData to production! This article explains what normal behaviour looks like so you can tell the difference between expected activity and genuine issues.
Notifications will appear continuously#
Once your integration is live, you will see notifications arriving in the Notifications tab. This is normal. Each notification represents a piece of data from your fundraising platform, such as a donation, profile update, or subscription change.
For webhook integrations, notifications arrive in real time as events happen on your platform. For polling integrations (such as JustGiving), notifications appear according to the polling schedule configured on your integration — for example, every 12 hours. Check your integration's article in this knowledge base for the specific schedule. For file-based integrations, notifications appear after each file upload.
Some notifications will be skipped#
You will notice that some notifications have a status of Skipped. This is expected behaviour, not an error.
MoveData skips notifications for several reasons:
- The data has already been processed (a duplicate notification was received).
- Your filtering rules excluded the notification.
- The notification type is not relevant to your configuration.
A Skipped status means MoveData evaluated the notification and decided no action was needed.
Processing time varies#
How quickly MoveData processes notifications depends on your integration type:
- Webhook integrations typically process in seconds.
- Polling integrations process within seconds of the polling cycle running, but the polling cycle itself may be scheduled hours apart (for example, every 12 hours). No notifications appear between polling cycles.
- File-based integrations may take several minutes depending on the file size.
The time it takes to process each individual notification is unique to your Salesforce org. This is influenced by a variety of factors, but particularly any flows, triggers, Apex tasks, Process Builder jobs, or other automation that runs on record save in your Salesforce org.
Note
During peak periods, you may see notifications briefly appear with a Processing or Queued status. They will resolve to Success, Skipped, or Failed once processing completes.
Duplicate detection is working#
MoveData uses a two-stage matching process to prevent duplicate records in Salesforce. First, it checks for a platform unique identifier. Then, it applies your Salesforce duplicate and matching rules. For more on how this works and how to configure it, see Duplicate rules.
If you see "matched" entries in the execution log, this means MoveData correctly identified an existing record. This is the system working as designed.
Error Notifications#
If you have Error Notifications enabled, MoveData sends you an email when a notification fails. This is your signal to investigate.
You can configure Error Notifications in Settings > General within the MoveData app. Enter your email address and click Update to enable them.
Warning
Always keep Error Notifications enabled. They are your primary alert mechanism for processing failures and should never be turned off. Ensure the receiving mailbox is checked regularly and that no spam filters or email rules are preventing MoveData error emails from being received.
What to monitor in the first week#
During your first week in production, we recommend the following routine:
- Check the Notifications tab daily. Look for any unexpected patterns, such as a sudden increase in failed notifications.
- Review failed notifications. Open each failed notification and read the execution log to understand the cause.
- Spot-check a few records in Salesforce. Open a few contacts, opportunities (NPSP) or gift transactions (Nonprofit Cloud), and campaigns to confirm data arrived correctly.
When to contact support#
Most issues resolve themselves or have simple fixes. However, you should contact MoveData support if:
- The same error repeats across many notifications.
- No notifications appear at all after the integration is connected.
- Data in Salesforce appears incorrect or incomplete after processing succeeds.
- You are unsure whether a particular behaviour is expected.
Success
Before contacting support, check Reading and understanding error messages for guidance on diagnosing common issues.
Reprocessing failed notifications#
If a notification fails, you do not lose the data. After resolving the underlying issue, you can reprocess the notification. Open the failed notification and click Reprocess to try again.
For more detail on diagnosing errors, see Reading and understanding error messages.