Error | Description | Solutions |
Data Rejected: Improper Format | Data sent FROM the system doesn't match the external system's format. For example, | Fix the source data in the original system or in the platform.
Update your inbound error filter to block improperly formatted data.
Use a dynamic formula to autocorrect. For example, append .com if missing. Note that this may involve guesswork. |
Data Rejected: Duplicate Entry | The external system requires unique values. For example, you have two users with the same email address. | Remove the duplicate in the external system.
Create a custom field for the email address in the destination system and map to it. |
Data Rejected: Missing Dependent Record | A record does not exist. For example, an SKU is missing. | Add or rename the SKU in the external system.
Update the SKU across all relevant systems. |
Error Filter Blocking Data | A mapping collection’s error filter prevents data from flowing (to/from the system). | Update the error filter to allow the data to pass.
Fix the data at its source to prevent future errors.
Exempt specific records/classes from the filter (if applicable). |
Partial Data Errors | Transfers will fail if any linked mapping fails. For example, a missing payment type causes a transaction to error. | Ensure all required data is present and valid before syncing. |
Error Filter Triggers Manual Retry | Errors created by filters require manual intervention. | Manually retry after addressing the root cause by fixing data or adjusting the filters. |