Overview
This article catalogs the error messages subscribers or their Managed Integration Service Provider (MiSP) may encounter when running the iPaaS.com Jasper PIM integration, what causes each one, and what to do about it. Your MiSP is the partner who owns your mappings, configuration, and credentials. Errors appear on the iPaaS.com Dashboard under Integration Monitoring, in the Error Logs.
Every error below carries a stable code in the form JASP-CATEGORY-NNNN — for example JASP-AUTH-1001. The code appears at the start of the message in your Error Logs, followed by the message text and a link back to this article. Codes never change once published, so the fastest way to find an entry here is to search this page for the code shown in your logs. A code with three segments, like JASP-EXTN-1001, comes from the Jasper PIM integration; a code with two segments, like NFND-1032, comes from the iPaaS.com platform and is documented separately.
Where a message shows a value in braces — for example {action} or {status} — Jasper PIM, iPaaS.com, or the integration fills in the specific detail at the moment the error is raised. The wording is otherwise exactly what appears in the Error Logs.
This integration writes to Jasper PIM. Every mapping collection moves data from iPaaS.com out to Jasper PIM, which is why several entries below describe operations in the reverse direction as unsupported. The integration also authors relatively little error text of its own: when Jasper PIM rejects a record, the integration passes Jasper PIM's own response through so you see exactly what Jasper PIM reported, now prefixed with the code that identifies where the failure occurred.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Connection and Authentication
Jasper PIM API Requests
Record Identifiers
Add/Update Jasper PIM Product Category FROM iPaaS.com
Webhook Subscription
Unsupported Operations
Error Collection
Connection and Authentication
The integration validates the connection to your Jasper PIM tenant before any transfer runs.
Connection to Jasper PIM could not be validated
JASP-AUTH-1001 - {the validation response returned by Jasper PIM}
Description: The integration checks the connection before transferring, and the check did not succeed. There is no fixed message text — what follows the code is the response Jasper PIM returned, so the wording varies with the underlying problem. The usual causes are an incorrect or expired API Key, an API Url that does not point at your tenant's API endpoint, 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, confirm the Jasper PIM tenant is reachable from a browser before treating this as an integration fault.
Jasper PIM API Requests
These errors are raised by the request layer and can surface in any flow. The action name inside the message identifies which request failed.
Jasper PIM returned an error response
JASP-EXTN-1001 - Error calling Jasper PIM during {action}: {response} (Http Code: {status})
Description: Jasper PIM returned a status other than success for the named request, and the integration includes Jasper PIM's own response and the HTTP status verbatim. The {action} portion names the request that failed. 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 response text after the action name — it is Jasper PIM's own explanation and usually identifies exactly what it objected to. Correct the source record in iPaaS.com, or the mapping that produces the field, then re-run the transfer. For a status of Unauthorized or Forbidden, re-check the API Key as described above. For TooManyRequests or a 5xx status the condition is usually transient: stagger bulk jobs rather than running large syncs concurrently.
Jasper PIM could not be reached
JASP-EXTN-1002 - {the transport error reported by the connection attempt}
Description: There is no fixed message text for this case: what follows the code is the transport error reported by the connection attempt, for example a name resolution failure, a connection timeout, or a TLS negotiation failure, and no HTTP status is present. The request never reached Jasper PIM. This points at an incorrect API Url, a network problem between iPaaS.com and Jasper PIM, or a Jasper PIM outage.
Resolution: Confirm API Url is the correct API address for your tenant. Confirm the Jasper PIM tenant is reachable from a browser. If Jasper PIM is up and the address is correct, the failure is between iPaaS.com and Jasper PIM rather than in the subscription settings — retry once, since transport failures are frequently transient.
Record Identifiers
Invalid record identifier
JASP-VALD-1001 - Invalid data passed to {Class}.SetPrimaryKey: {value}
Description: A record identifier supplied for a transfer was not in the form the integration expects for that record type. The rejected value is shown at the end of the message. This most often follows a manual sync submitted with a mistyped identifier, or a mapping that produces an identifier in an unexpected format.
Resolution: Compare the value shown in the message against the identifier as Jasper PIM reports it, and re-submit using the exact form. If the value came from a mapping rather than a manual entry, review the mapping that produces the record identifier for that collection.
Add/Update Jasper PIM Product Category FROM iPaaS.com
This 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 has not been transferred yet
JASP-BIZL-1001 - Parent category must be uploaded first
Description: 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.
Webhook Subscription
Jasper PIM connection unavailable during webhook setup
JASP-INTL-1001 - Unable to locate Jasper Call Wrapper while updating Webhook Subscription
Description: The integration registers webhook subscriptions with Jasper PIM so changes can be picked up. This error means the connection to Jasper PIM was not available at the moment the subscription was being registered, so the registration did not complete.
Resolution: This is an integration-level failure rather than something to correct in the subscription settings. Confirm the connection settings are valid — an unresolved JASP-AUTH-1001 in the same run points at the same cause — then re-save the subscription so registration is attempted again. If the connection is otherwise healthy and this recurs, contact iPaaS.com Support at support@ipaas.com.
Unsupported Operations
Several operations are deliberately not implemented in this integration. When one of them is invoked — usually because a mapping collection or a subscription event was configured to attempt it — the attempt fails with the code below. These are configuration errors rather than faults, and the fix is always to stop the operation being attempted rather than to retry it.
Deleting a product category is not supported
JASP-BIZL-1002 - Deleting a Jasper PIM product category from iPaaS.com is not supported.
Description: The integration creates and updates Jasper PIM product categories but never deletes them, so a delete attempt fails and nothing is removed in Jasper PIM.
Resolution: Remove the category in Jasper PIM instead, and confirm no delete event is enabled against the Product Category collection. Deleting the record in iPaaS.com removes only the iPaaS.com record; the two sides must be reconciled by hand.
Deleting a product is not supported
JASP-BIZL-1003 - Deleting a Jasper PIM product from iPaaS.com is not supported.
Description: The integration creates and updates Jasper PIM products but never deletes them, so a delete attempt fails and nothing is removed in Jasper PIM.
Resolution: Remove or deactivate the product in Jasper PIM instead, and confirm no delete event is enabled against the Product collection.
Deleting a product option is not supported
JASP-BIZL-1004 - Deleting a Jasper PIM product option from iPaaS.com is not supported.
Description: Product options are created and updated in Jasper PIM but never deleted by the integration, so a delete attempt fails.
Resolution: Remove the option in Jasper PIM instead, and confirm no delete event is enabled against the Product Option or Product Variant Option collections, which share this behavior.
Deleting a product option value is not supported
JASP-BIZL-1005 - Deleting a Jasper PIM product option value from iPaaS.com is not supported.
Description: Product option values are created and updated in Jasper PIM but never deleted by the integration, so a delete attempt fails.
Resolution: Remove the option value in Jasper PIM instead, and confirm no delete event is enabled against the Product Option Value or Product Variant Option Value collections, which share this behavior.
Deleting product inventory is not supported
JASP-BIZL-1006 - Deleting Jasper PIM product inventory from iPaaS.com is not supported.
Description: Inventory records are created and updated in Jasper PIM but never deleted by the integration, so a delete attempt fails.
Resolution: Adjust the inventory quantity in Jasper PIM rather than deleting the record, and confirm no delete event is enabled against the Product Inventory or Product Variant Inventory collections.
Deleting a product variant is not supported
JASP-BIZL-1007 - Deleting a Jasper PIM product variant from iPaaS.com is not supported.
Description: Product variants are created and updated in Jasper PIM but never deleted by the integration, so a delete attempt fails.
Resolution: Remove the variant in Jasper PIM instead, and confirm no delete event is enabled against the Product Variant collection.
Reading product inventory into iPaaS.com is not supported
JASP-BIZL-1008 - Reading Jasper PIM product inventory into iPaaS.com is not supported. This integration writes inventory to Jasper PIM only.
Description: This integration is outbound: inventory flows from iPaaS.com to Jasper PIM. Reading inventory back out of Jasper PIM is not implemented, so the attempt fails and no Jasper PIM call is made.
Resolution: Confirm the Product Inventory and Product Variant Inventory collections are configured FROM iPaaS.com only, and that no collection is set to capture inventory from Jasper PIM. iPaaS.com is the system of record for the values this integration sends.
Reading product variants into iPaaS.com is not supported
JASP-BIZL-1009 - Reading Jasper PIM product variants into iPaaS.com is not supported. This integration writes variants to Jasper PIM only.
Description: This integration is outbound: variants flow from iPaaS.com to Jasper PIM. Reading variants back out of Jasper PIM is not implemented, so the attempt fails and no Jasper PIM call is made.
Resolution: Confirm the Product Variant collection is configured FROM iPaaS.com only, and that no collection is set to capture variants from Jasper PIM.
Getting Further Help
If a message in the Error Logs is not listed here, or the resolution above does not clear it, contact iPaaS.com Support at support@ipaas.com. Include the subscription name, the error code, the mapping collection involved, the full text of the message from the Error Logs, and the time the error occurred, so the run can be traced.