Error handling is one of the most important aspects of maintaining a healthy data integration. Knowing when to let a transfer continue despite errors, and how to interpret and resolve data errors effectively, keeps your integrations running smoothly without letting problems go unnoticed.

This guide covers best practices for using Continue on Error, reading and understanding data error logs, and safely reprocessing records after fixing root causes in MyRapidi.

In the 7th Session of our Open Office Hours series, we cover Continue on Error and Data Errors in Rapidi.

When we introduced Albert in 2025, it was a bold step: an AI assistant that didn't just answer questions but actually executed tasks within your MyRapidi interface. Nearly a year later, Albert has grown from a promising beta into a comprehensive integration management assistant. Here's everything that's new.

When Rapidi runs a transfer, it doesn't pull all your data every time. It only pulls what changed since the last run. That keeps your source systems from getting hammered with unnecessary queries. But how does it actually know what changed? The answer is two things working together: source control fields and the RTI.