External System Rejects the Data: Data is Improperly Formatted
In this case, data going FROM iPaaS.com is not formatted in the way the destination system expects. For instance, the destination system might validate that data in an “E-Mail” field is properly formatted as an address and the data in iPaaS.com is “John@test” instead of “John@test.com”. To address this:
Updates could be made on the inbound error filter to stop this data from getting to iPaaS.com.
The data could be fixed in the source system or iPaaS.com directly.
A dynamic formula could be written to convert this to an email address if the TLD (i.e. .com) is left off (but in this case the system would be making a guess about it being .com, it could not know that for sure).
External System Rejects the Data: Data is a Duplicate
In this case, data going FROM iPaaS.com is trying to create a field that the destination system only allows for a unique value. For instance, the destination system might only allow for one customer to have a unique email address, so if you try to update another customer record with that same email address you will see an error message. In order to resolve:
Remove the email address in the destination system.
Create a custom field for an email address in the destination system (if allowed) and map to it.
External System Rejects the Data: Dependent Record Not Present
In this case, data going FROM iPaaS.com is trying to create a transaction in Magento and it wants to reference a SKU that is not present. In order to resolve:
Add the SKU to the external system.
Rename the SKU in the external system.
Update the SKU in any systems where this product may reside.
External System Rejects the Data: Dependent Data Not Present
In this case, data going FROM iPaaS.com is trying to update a variant where we have an external ID in iPaaS.com but Magento is reporting it is not present. In order to resolve:
Add the variant to the external system.
Manually sync and retry.
An error filter is in place on the mapping collection
In this case, data going TO or FROM iPaaS.com has an error filter on the mapping collection that is showing an error for this data. This error filter could be updated to allow records to pass and/or the data should be updated in the origin system to prevent this from happening again. In certain cases, the error filter could be updated to not apply to this record (or class of records).
Partial Data
When a webhook is processed all associated mappings need to be able to be processed in order for it to not to error. For instance,
If one product attribute errors, the entire product will error.
If a payment type type is not present, the transaction will error.
Error from Error Filter
When an error is created by an error filter it will require a manual retry. Here is an example of what that looks like:
