Continue on Error

When Rapidi runs a transfer and a record fails, the default behaviour is to stop the entire run. Continue on Error changes this: Rapidi logs the failed record and keeps processing the rest, so one bad record doesn't block your entire sync.

When to Use It

Enable it when you have large data sets where occasional errors are expected and shouldn't hold up everything else. Avoid relying on it during initial integration setup - errors at that stage are usually systematic and need immediate attention, not just logging.

How to Enable It

Go to Transfers → Open the relevant Transfer → General → Edit → Enable Continue on Error → Save.

⚠️ Important: If any of your field mappings use an ERROR formula, Continue on Error will not work for those mappings. The error formula takes precedence and will stop the record from being processed regardless of this setting. 

Monitoring – Data Errors Page

  • Once enabled, failed records are logged under Logs → Data Errors. Each entry shows the DateTime, Transfer, Source, Destination, a Description, and the specific record.
  • Use the filters to find what matters: filter by Error Status (Resolved/Unresolved) as your main triage tool, narrow by Transfer, Date/Time, or Source/Destination connection.

Notifications

  • Rapidi does not send automatic notifications when data errors occur. If you would like to receive notifications when errors are logged, contact us - we can set up separate error notifications for you.

Actions

  • On individual entries you can add a comment, mark as resolved (red → green), or jump directly to the Transfer. For bulk management, select multiple entries to Change Resolved, Export JSON, or Delete. Use Delete with caution - it's permanent.