This article lists the error messages you may encounter with the iPaaS.com Jasper PIM integration. These errors appear under Dashboard / Integration Monitoring / Error Logs, where you can identify, understand, and resolve issues encountered during data synchronization.
The Jasper PIM integration writes very little error text of its own. Most failures a subscriber sees during a transfer are the message Jasper PIM itself returned, passed through unchanged so you see exactly what Jasper PIM reported. The sections below cover the one validation message the integration raises on its own, followed by how connection and Jasper PIM API errors appear and what to do about them.
Product Category Transfers
The Add/Update Jasper PIM Product Category FROM iPaaS.com collection transfers your category hierarchy into Jasper PIM. Because a child category cannot be placed correctly until its parent exists, the collection checks the parent before each category transfers.
Parent category not yet transferred
"Parent category must be uploaded first"
Explanation: Before a category transfers, the collection checks whether it has a parent category. If it does, the collection looks for that parent's link to a Jasper PIM record. When the parent has not been transferred yet, no link exists, and the transfer is stopped rather than creating a category in the wrong place in the hierarchy. Categories without a parent — top-level categories — are unaffected and transfer normally.
Resolution: Transfer the parent category first, then re-sync the child. Category hierarchies transfer from the top down, so when you sync several categories together, re-running the sync after the parent has landed usually clears the error. If the parent has already been transferred and you still see this message, confirm the parent category in iPaaS.com is linked to its Jasper PIM record. This check is part of the mapping collection's Filter, so subscribers or their MiSP can review and adjust it in iPaaS.com.
Connection and Jasper PIM API Errors
The messages in this section are not written by the integration. The integration reports the text Jasper PIM returned, so the exact wording comes from Jasper PIM and varies with the underlying problem.
Connection to Jasper PIM cannot be established
The integration validates the connection to your Jasper PIM tenant before any transfer runs. When that validation does not succeed, the transfer stops and the error log shows the response Jasper PIM returned.
Explanation: The integration could not reach your Jasper PIM tenant or was not accepted by it. The usual causes are an incorrect or expired API Key, an API Url that does not point at your tenant's
/api/v1endpoint, or the tenant being temporarily unreachable.Resolution: Check the API Url and API Key subscription settings against your Jasper PIM tenant, following the Jasper PIM Connections and Settings article. Confirm the API Key is still active in Jasper PIM and has not been revoked or regenerated. If the settings are correct and the error continues, confirm your Jasper PIM tenant is reachable, then contact iPaaS.com Support.
Jasper PIM rejects a record during a transfer
When Jasper PIM declines to create or update a record, the integration reports Jasper PIM's own response for that record.
Explanation: Jasper PIM rejected the record it was sent. Common causes are a required field arriving empty, a value that does not match what Jasper PIM expects for that field, or a referenced record that does not exist in Jasper PIM yet.
Resolution: Read the message text in the error log — it identifies what Jasper PIM objected to. Correct the source record in iPaaS.com or the mapping that produces the field, then re-sync. If the message points at a field you do not recognize or does not make the cause clear, contact iPaaS.com Support with the error log entry.