When an integration does not behave as expected, knowing where to look first saves time and prevents unnecessary troubleshooting steps. Logs and runs in MyRapidi give you a complete picture of what happened during each transfer execution, helping you quickly and accurately isolate problems.
This guide covers how to read and interpret run logs, navigate the logs interface, isolate issues across source, mapping, and destination layers, and use filters to find exactly what you need in MyRapidi.
In the 8th Session of our Open Office Hours series, we cover Logs & Runs: Your Troubleshooting Toolkit in Rapidi.
Logs & Runs: Your Troubleshooting Toolkit
Quick Summary:
In this Open Office Hours session, we walk through how to use logs and runs in MyRapidi to troubleshoot and monitor your data integrations effectively.
Topics covered include:
- Where to look first – How to quickly identify which part of your integration needs attention when something goes wrong
- Understanding run logs – How to read and interpret the information in each transfer run to understand what happened
- Isolating problems – How to determine whether an issue originates in the source system, field mappings, or the destination system
- Using filters effectively – How to narrow down log entries to find the specific information you need for faster troubleshooting
We also share practical tips on building a systematic troubleshooting approach to resolve integration issues efficiently.
Watch the Replay of our eighth session: Logs & Runs: Your Troubleshooting Toolkit
Logs & Runs in RAPIDI: Your Complete Troubleshooting Toolkit
Every time a transfer executes in Rapidi, it creates a run record with detailed logs about what happened. These logs are your primary diagnostic tool when something does not work as expected. Understanding how to navigate and interpret them is essential for maintaining healthy integrations.
Where to Look First
When you notice an issue with your integration, the first step is knowing where to start. MyRapidi provides several entry points for investigating problems.
Starting from the transfer overview
- Check the transfer status – A quick glance at the transfer list shows whether recent runs completed successfully, with errors, or failed entirely
- Look at the last run time – If a scheduled transfer has not run recently, the schedule or trigger may need attention
- Review the record count – An unexpected number of processed records (too many or too few) often signals a filter or criteria issue
Quick triage checklist
- Is the transfer running at all? (Check schedule and status)
- Did the last run complete? (Check run status)
- Were the expected records processed? (Check record counts)
- Are there data errors? (Check the error log)
Understanding Run Logs
Each transfer run in MyRapidi generates a detailed log that records every step of the process. Learning to read these logs efficiently is key to fast troubleshooting.
What a run log contains
- Run status – Whether the run completed successfully, completed with errors, or failed
- Start and end time – How long the run took, which helps identify performance issues
- Records processed – How many records were read from the source, how many were created or updated in the destination
- Errors and warnings – Any issues encountered during the run, with details about which records were affected
Reading the log timeline
Run logs present events in chronological order. For each record processed, you can see:
- The source record that was read
- The field mappings that were applied
- The destination operation that was attempted (create, update, or skip)
- The result of that operation (success or error with details)
Isolating Problems Across Systems
Integration issues can originate in three places: the source system, the field mappings, or the destination system. The logs help you determine which layer is responsible.
1) Source system issues
Problems reading data from the source system. Common indicators:
- Connection errors or timeouts when accessing the source API
- Fewer records returned than expected, suggesting filter or permission issues
- Unexpected data values that do not match the expected format
2) Mapping issues
Problems transforming data between source and destination formats. Common indicators:
- Formula errors in field mappings (e.g., LOOKUP returning blank values)
- Data type mismatches between source and destination fields
- Missing or incorrect constant values
3) Destination system issues
Problems writing data to the destination system. Common indicators:
- Validation errors from the destination API
- Permission denied errors for the integration user
- Duplicate record conflicts or missing required fields
Using Filters Effectively
When dealing with large volumes of log data, filters help you find exactly what you need without scrolling through hundreds of entries.
Filtering by status
- Filter for errors only to focus on records that need attention
- Filter for successful records to verify that expected data is flowing correctly
- Filter for warnings to catch potential issues before they become errors
Filtering by date and time
- Narrow down to a specific run or time window when an issue was reported
- Compare runs from different dates to identify when a problem first appeared
Filtering by record
- Search for a specific record by its identifier to trace its journey through the integration
- Track a single record across multiple runs to understand its history
Building a Troubleshooting Routine
A systematic approach to troubleshooting saves time and ensures problems are resolved at their root cause rather than just their symptoms.
Recommended troubleshooting steps
- Identify the symptom – What is not working as expected? Missing data, wrong values, errors?
- Check the run log – Find the relevant run and review its status, record counts, and any errors
- Isolate the layer – Is the issue in the source data, the mapping logic, or the destination system?
- Reproduce if possible – Run the transfer manually with a small data set to confirm the issue
- Fix and verify – Apply the fix and run again to confirm the issue is resolved
Summary
Logs and runs are your most powerful tools for understanding and troubleshooting data integrations in Rapidi. Start by checking the transfer overview for quick status information, then dive into run logs to understand exactly what happened. Use the three-layer isolation approach (source, mapping, destination) to pinpoint where issues originate, and leverage filters to navigate large log volumes efficiently. Building a consistent troubleshooting routine ensures you resolve issues quickly and prevent recurrence.
What's Next
Stay tuned for the next session in our Open Office Hours series. Each week, we cover a new topic to help you get the most out of your Rapidi integration.
Can't attend live? Register anyway, and we'll send you the recording and materials afterward.
Frequently Asked Questions
What are runs in MyRapidi?
A run is a single execution of a transfer. Every time a transfer runs, whether manually triggered or on a schedule, MyRapidi creates a run record that logs everything that happened: how many records were read, how many were created or updated, any errors encountered, and the overall status. Runs give you a complete audit trail of your integration activity.
Where do I find the logs for a specific transfer?
Navigate to the transfer in MyRapidi and look for the Runs or Log section. Each run is listed with its date, status, and record counts. Click into a run to see the detailed log entries for each record processed. You can also access logs from the main dashboard if a transfer shows errors or warnings.
How do I tell if an error is from the source or destination system?
The run log shows each step of the process separately. If the error occurs during data reading, it is a source issue. If it occurs during field mapping or formula evaluation, it is a mapping issue. If it occurs when writing to the destination, it is a destination issue. The error message usually includes the system name and specific API error to help you identify the layer.
Can I filter logs to find a specific record?
Yes. MyRapidi's log viewer supports filtering by record identifier, date range, status, and error type. This lets you trace a specific record through the integration, find all errors in a particular time window, or focus on a specific type of issue. Filtering is especially useful when dealing with high-volume transfers that generate many log entries.
What should I do if a transfer runs but no records are processed?
A run with zero records processed usually indicates a filter or criteria issue. Check the transfer's source criteria and filters to ensure they match the records you expect to sync. Also verify that the source system has records that meet the criteria, and that the integration user has permission to read them. If timestamps are used, confirm the last sync timestamp is correct.
