Overview
This article catalogs the error messages the Kuehne+Nagel integration can produce, grouped by the mapping collection flow that raises them. Each entry gives the message as it appears in iPaaS.com, what causes it, and how to resolve it. Errors appear in Dashboard / Integration Monitoring / Error Logs.
Some conditions that stop a transfer are configuration requirements rather than error messages in their own right — most notably the requirement that the shipping method mapped by this integration already exists in iPaaS.com. Those are covered in the Kuehne+Nagel to iPaaS.com Transaction Tracking Number Mapping Documentation and in the mapping collection description, alongside the setup steps that prevent them.
Supported Flows
Add/Update Kuehne+Nagel Transaction Tracking Number TO iPaaS.com
Add/Update Kuehne+Nagel Transaction Tracking Number TO iPaaS.com
Invalid Shipment Identifier
Could not transfer because the Shipment Id was not provided in the correct format. Expected format: {BlNumber}|{Scac}
Description: The shipment identifier supplied for the transfer is not in the form the integration expects. It occurs most often on a Manual Sync where the value entered is missing the pipe separator, is missing one of the two parts, or has extra spacing. The transfer stops before any call is made to Kuehne+Nagel.
Resolution: Re-enter the identifier as the Bill of Lading number and the carrier SCAC code joined by a pipe character, with nothing either side of it — for example KN123456789|KUEH. Both parts are required.
Missing Reference Number
Could not transfer because the Kuehne+Nagel shipment has no Reference Number. Shipment Id: {ShipmentId}
Description: Kuehne+Nagel returned the shipment, but the record carries no Reference Number. The integration uses the Reference Number to find the iPaaS.com Transaction the tracking record belongs to, so without it there is nothing to attach the shipment to. The message names the shipment identifier that failed, so you can identify the shipment directly from the log entry.
Resolution: Add the Reference Number to the shipment in Kuehne+Nagel so that it carries the order reference used in iPaaS.com, then transfer the shipment again. If the shipment legitimately has no order reference, it cannot be tracked against an iPaaS.com Transaction and should be excluded from the transfer.
No Matching Transaction
Could not transfer because no iPaaS.com Transaction has Transaction Number {ReferenceNumber}. Kuehne+Nagel Shipment Id: {ShipmentId}
Description: The shipment carries a Reference Number, but no iPaaS.com Transaction has a Transaction Number matching it. The match is exact — a difference in case, spacing, or leading zeros is enough to prevent it. The message names both the Transaction Number that was searched for and the shipment identifier that failed.
Resolution: Confirm the Transaction exists in iPaaS.com and that its Transaction Number matches the shipment's Reference Number exactly, then transfer the shipment again. This integration never creates the Transaction — it only attaches tracking to one that is already present, so the Transaction must be transferred into iPaaS.com first by whichever integration owns it.
Kuehne+Nagel Rejected the Request
Error calling Kuehne+Nagel {operation}: {response body} (Http Code: {status})
Description: Kuehne+Nagel returned a failure response rather than shipment data. The message carries the operation that was attempted, the response Kuehne+Nagel sent back, and the HTTP status code. The most common causes are credentials that Kuehne+Nagel does not accept, an account whose API access has not been approved or has lapsed, and requests for a shipment the account is not entitled to see. Because the integration does not validate credentials when the subscription is saved, an incorrect Authentication_Id, Client_Code, or UserName first surfaces here rather than at setup.
Resolution: Check the status code and response text in the log entry. For a rejection that mentions authentication or authorization, re-check the three credential values in the subscription settings against those issued by the Kuehne+Nagel Helpdesk, and confirm with the Helpdesk that API access is still active for your account. For a rejection that names the shipment, confirm the shipment exists and is visible to your Kuehne+Nagel account. If the response is unclear or the failure persists with confirmed-correct credentials, contact iPaaS.com Support at support@ipaas.com.
Could Not Reach Kuehne+Nagel
The message returned by the failed connection, passed through unchanged — for example, "No such host is known." or "The operation has timed out."
Description: The request to Kuehne+Nagel could not be completed at all, so there is no response to report. This is a transport-level failure rather than a rejection: the address could not be resolved, the connection timed out, or the secure connection could not be established. The most common configuration cause is an API Url that is incorrect or points somewhere unreachable from iPaaS.com.
Resolution: Confirm the API Url in the subscription settings is the address supplied by Kuehne+Nagel. If it is correct and the failure repeats, the Kuehne+Nagel API may be temporarily unavailable — retry the transfer later. If it continues, contact iPaaS.com Support at support@ipaas.com.
iPaaS.com Rejected the Transaction Lookup
The message returned by iPaaS.com for the failed request, passed through unchanged.
Description: While searching iPaaS.com for the Transaction matching the shipment's Reference Number, iPaaS.com returned an error instead of a result. This is distinct from finding no match — it means the lookup itself did not complete. It is usually a transient platform condition rather than something in the shipment data.
Resolution: Retry the transfer. If the same error repeats, contact iPaaS.com Support at support@ipaas.com with the log entry.