The error log is where you diagnose and resolve data transfer problems in iPaaS.com. When a record fails to sync, it surfaces here with the detail you need to understand what happened and act on it. The debug tools on the manual sync and record pages give you additional ways to work through issues.
Reading the Error Log
Each error entry identifies the record and transfer involved, the direction, and the reason for the failure. From an entry you can navigate directly to the related record - and, where the failure is on a specific product variant, directly to that variant - so you can inspect the data that caused the problem without hunting for it.
Actions on the Error List
Refresh: Refresh the list of errors.
Export to CSV: Export the current error list to CSV for offline review, sharing, or tracking.
Bulk Retry: Retry selected errors.
Bulk Dismiss: Dismiss selected errors.
Actions on Errors
Open the record: Jump straight to the related iPaaS.com record (or variant) from the error.
View the original error: See what the first error was, as a retry could change the error.
Retry: Reprocess a failed transfer using the retry icon, once you've addressed the underlying cause.
Debug: Re-run the transfer with details to better understand what happened.
Dismiss: Clear an error you've handled or that no longer applies. Errors can be dismissed from the manual sync and debug pages.
Error Flags Elsewhere
Errors also surface outside the log. External ID listings can show an error flag on records that failed to transfer, so you can spot problem records in context while working in a data model. See External IDs.