Overview
This document catalogs the error messages a subscriber may encounter when synchronizing data with ShipHawk, grouped by mapping collection flow, along with what causes each error and how to resolve it. Errors appear in iPaaS.com under Dashboard > Integration Monitoring > Error Logs.
Supported Flows
Add/Update ShipHawk Shipment TO iPaaS.com
Add/Update ShipHawk Order FROM iPaaS.com
Connection
Add/Update ShipHawk Shipment TO iPaaS.com
Tracking not linked to a transaction
Error message: ShipHawk Shipment Tracking Number is not linked to any existing iPaaS.com Transaction
Description: the shipment's order has no matching transaction in iPaaS.com, so the tracking record cannot be attached to it.
Resolution: confirm the order was transferred to iPaaS.com and its transaction exists before syncing the shipment.
Shipping method does not exist
Error message: Shipping Method {Carrier} needs to be created manually in iPaaS.com first
Description: the shipment's carrier does not match a Shipping Method configured in iPaaS.com. The carrier comparison is case-sensitive.
Resolution: create the Shipping Method in iPaaS.com with the exact carrier name (including letter casing), then re-run the sync.
Unable to link tracking number
Error message: Unable to dynamically link to existing iPaaS Transaction Tracking using Tracking Number of iPaaS matching with Tracking Number of ShipHawk. This may result in duplicate transaction tracking records.
Description: a matching tracking record could not be resolved on the transaction, which can lead to duplicate tracking records.
Resolution: confirm the order and its existing tracking are correct in iPaaS.com. If duplicate tracking records appear, contact iPaaS.com Support.
Add/Update ShipHawk Order FROM iPaaS.com
Unable to link order line
Error message: Unable to dynamically link to existing ShipHawk Sales Order Line using Transaction Number. This may result in duplicate Transaction Line records.
Description: a line item could not be matched to an existing ShipHawk order line, which can lead to duplicate line items. Line items are matched by external ID, and by SKU when no external ID is present.
Resolution: ensure the order transferred successfully so its external ID exists, and confirm SKUs are consistent between iPaaS.com and ShipHawk. If duplicate line items appear, contact iPaaS.com Support.
Connection
ShipHawk connection unavailable
Error message: Unable to locate ShipHawk Call Wrapper
Description: the integration could not establish the ShipHawk connection, usually because the connection is not configured or the credentials are missing.
Resolution: confirm the API Url and API Key are set correctly on the ShipHawk subscription settings in iPaaS.com.
Invalid API Key
Error message: X-Api-Key header is missing or invalid
Description: the ShipHawk API Key in the iPaaS.com Subscription Settings is missing, expired, or incorrect.
Resolution: generate a new API Key in the ShipHawk portal under Settings > Developer API and update the API Key field on the subscription.