How to reprocess failed notifications
When a notification fails, MoveData does not discard it. The data stays in the notification, ready for you to fix the underlying problem and reprocess it. Reprocessing re-runs the full processing pipeline from scratch.
Before you begin#
- Read the error message on the failed notification to understand the root cause.
- Fix the underlying issue before you reprocess. See Reading and understanding error messages for guidance.
- You may also want to check Setup > Process Automations > Flows > Failed Flow Interviews in Salesforce for additional error details related to flow processing failures.
Danger
Always fix the root cause of the error before you reprocess. Reprocessing without fixing the problem produces the same error again.
When to reprocess#
Reprocess a notification after you have:
- Fixed a Salesforce validation rule that was blocking the record.
- Corrected field mappings or data issues.
- Updated permissions for the MoveData Authorised User.
- Resolved any other issue described in the error message.
If you are unsure what caused the failure, start by reading the error message and execution log. See Reading and understanding error messages for guidance.
Reprocess from the list view#
- Open the Notifications tab in the MoveData app.
- Find the failed notification in the list.
- Click the dropdown arrow on the right side of the notification row to open the context menu.
- Select Reprocess.
Success
Use the Failed Notifications list view to quickly find all notifications that need attention. Select it from the list view dropdown at the top of the Notifications tab.
Reprocess from the detail view#
- Open the Notifications tab in the MoveData app.
- Click the failed notification to open its detail view.
- Click the Reprocess button.
What happens during reprocessing#
When you reprocess a notification, MoveData:
- Creates a new notification based on the original payload data.
- Runs the full processing pipeline on the new notification.
- Applies all current field mappings, duplicate rules, and extensions.
- Sets the new notification status to Success, Failed, or Skipped based on the outcome.
Note
Reprocessing creates a new notification — the original notification's status does not change. This is by design. Each notification is a time-stamped log of what happened at that point in time, so you will have two notifications: the original (still showing Failed) and the reprocessed version.
Note
Reprocessing uses your current configuration, not the configuration that was active when the notification first arrived. If you have changed field mappings or rules since the original failure, the new settings apply.
What to check after reprocessing#
After you reprocess a notification, verify that it completed successfully:
- Open the notification and check that the status is now Success.
- Review the Records tab to confirm that the expected Salesforce records were created or updated.
- If the status is still Failed, read the new error message — it may be a different issue.
Reprocessing multiple notifications#
Bulk reprocessing is not a built-in feature. To reprocess multiple failed notifications, the fastest approach is:
- Filter the Notifications tab by Status = Failed (and optionally by integration).
- Open each failed notification in a new browser tab.
- Click Reprocess on each one.
Fix the underlying issue first, then work through the failed notifications.
Note
If the volume of failed notifications is too large to reprocess manually, contact support@movedata.io. MoveData may be able to assist with automated reprocessing depending on the volume. For large-scale historical data, see Data Imports.