In our ongoing effort to provide our customers with a better experience when submitting support tickets, we have now moved our support system to MyRapidi. From today, support is built directly into MyRapidi. You will be able to see your submitted cases within the same system you use for your integration setup.

How to Use Logs and Runs in MyRapidi to Troubleshoot Your Integration

When your integration throws an error, the first question is always the same: where do I look? In MyRapidi, logs and runs give you that answer. They show exactly what happened, which transfer caused it, how long it took, and what the error message says. Once you know how to read them, troubleshooting becomes a lot faster.

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.