Skip to main content
Deutsch (Deutschland) Español Français (France) Italiano Polski Slovenčina (Česko)

Search

search shadow

Articles in this section

See more

Ocean Shipment Tracking Errors and Recommended Actions

Rich Hellinga
Rich Hellinga
Updated

In this article

The table below lists the Ocean shipment tracking Root Cause Analysis (RCA) errors and the recommended actions for fixing those issues.

Root Cause Error

Recommended Actions

Carrier Sent Empty or Invalid Data

Issue: The carrier's response for the last shipment tracking update request from project44 was empty or invalid

Recommended Action:

  1. It appears that the carrier might not have updated the tracking information for your shipment yet.

  2. In case you believe that the tracking information should have been available by this time, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

No Tracking Information Found via API

Issue: No information corresponding to the provided shipment identifiers was found with the carrier.

Recommended Action:

  1. It appears that the carrier might not have dispatched the shipment yet.

  2. In case you believe that the shipment was expected to be dispatched by this time, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Pending Tracking Information from the Carrier

Issue: This is a recently created shipment, and project44 has not received any tracking updates from the carrier yet.

Recommended Action:

  1. Wait for a period of at least 15 days from the date of booking creation for tracking information to become available.

  2. After this period, if you still do not have access to the tracking information and believe it should have been available, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Shipment Data Not Found and No API Access

Issue: No information corresponding to the provided shipment identifiers was found with the carrier.

Additionally, the carrier has not provided project44 with a reliable API connection for accessing the customer's shipment tracking information. This could affect data consistency and completeness due to carrier limitations.

Recommended Action:

  1. It appears that the carrier might not have dispatched the shipment yet.

  2. In case you believe that the shipment was expected to be dispatched by this time, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

You can enhance your data quality if your carrier establishes an API connection with project44.

  1. Submit a request to the carrier for an API connection.

  2. If the carrier has an existing API connection with project44 that is not enabled for your account, they can work with project44 to facilitate its setup.

  3. If the carrier does not have an API integration, they may need to develop a new one.

CTA: Request API Access

Inconsistent Data Received from Carrier

Issue: The carrier has not provided project44 with a reliable API connection for accessing the customer's shipment tracking information. This could affect data consistency and completeness due to carrier limitations.

Recommended Action: You can enhance your data quality if your carrier establishes an API connection with project44.

  1. Kindly submit a request to the carrier for an API connection.

  2. If the carrier has an existing API connection with project44 that is not enabled for your account, they can work with project44 to facilitate its setup.

  3. If the carrier does not have an API integration, they may need to develop a new one.

CTA: Request API Access

Carrier Yet to Assign Container

Issue: The carrier has not yet assigned container information to this shipment.

Recommended Action:

  1. It appears that the details of the container are currently unavailable, possibly because the carrier has not yet dispatched the shipment.

  2. In case you believe that the shipment was expected to be dispatched by this time, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Carrier Does Not Support Given Shipment Identifier

Issue: The provided shipment identifier in the creation request is not supported by the carrier.

Recommended Action:

  1. Contact your carrier to acquire the list of supported shipment identifiers applicable to your customer account.

  2. Retry the shipment creation using a supported shipment identifier type for this carrier.

  3. If the problem persists after retrying, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Expired Shipment

Issue: No carrier updates received over a prolonged time period has led to the expiration of the shipment.

Recommended Action:

  1. Despite project44's repeated attempts, no tracking updates were received from the carrier for an extended duration, leading to the shipment being marked as expired.

  2. In case you believe that the tracking information should have been available for this shipment, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Carrier Connection Timed Out

Issue: The carrier could not provide a shipment tracking update within the permitted time limit following project44's request.

Recommended Action:

  1. project44 will continue its retry attempts to fetch data from the carrier and address the issue at hand.

  2. If you notice that this issue is continuously affecting a significant number of your shipments over an extended time period, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Temporary Service Disruption

Issue: There was a temporary service interruption.

Recommended Action: If you notice that this issue is continuously affecting a significant number of your shipments over an extended time period, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Unknown Error

Issue: The cause of this error is yet to be determined by project44, but the team remains proactive in regularly introducing new root causes.

Recommended Action: If you notice that this issue is continuously affecting a significant number of your shipments over an extended time period, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Carrier Facing Technical Issues

Issue: The carrier returned a technical error message in response to project44's shipment tracking update request.

Recommended Action:

  1. project44 will collaborate with the carrier to identify the issue and initiate the reprocessing of the shipment tracking update.

  2. If you notice that this issue is continuously affecting a significant number of your shipments over an extended time period, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Invalid Shipment Identifier

Issue: The provided shipment identifier in the creation request is empty or invalid.

Recommended Action:

  1. Please review and ensure that the shipment identifier specified in the creation request is accurate.

  2. If needed, kindly proceed to recreate the shipment creation request with the accurate identifier.

No Carrier Updates Received for 30 Days

Issue: project44 has not received any tracking updates from the carrier during the 30-day period since the shipment was created.

Recommended Action:

  1. It appears that the carrier might not have dispatched the shipment yet.

  2. In case you believe that the shipment was expected to be dispatched by this time, kindly reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Subscription On Hold

Issue: As per the customer's request, the tracking of the shipment has been put on hold.

Recommended Action: No further action is necessary as this behavior was expected.

No Carrier Updates Received for 60 Days

Issue: project44 has not received any tracking updates from the carrier during the 60-day period since the shipment was created

Recommended Action:

  1. It appears that the carrier might not have dispatched the shipment yet.

  2. In case you believe that the shipment was expected to be dispatched by this time, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

No Carrier Updates Received for 80 Days

Issue: project44 has not received any tracking updates from the carrier during the 80-day period since the shipment was created.

Recommended Action:

  1. It appears that the carrier might not have dispatched the shipment yet.

  2. In case you believe that the shipment was expected to be dispatched by this time, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Carrier Rejected Customer Login Credentials

Issue: The carrier rejected the login credentials provided for the customer.

Recommended Action:

  1. Check the expiration date of the login credentials provided by the carrier and, if necessary, contact the carrier for new credentials.

  2. When the new login credentials are available, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Carrier Denied Access for Customer

Issue: The carrier has refused access to data for this customer.

Recommended Action:

  1. Reach out to the carrier to enable the authorization for access.

  2. If access has been granted for your account by the carrier, kindly retry the shipment creation request for reprocessing.

  3. If the problem persists after retrying, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Carrier Blocking API Requests for Customer - Private Connection

Issue: The carrier has imposed a rate limit on the customer account for fetching shipment tracking information and project44 has exceeded that limit.

Rate limit refers to the maximum number of shipment tracking requests allowed by the carrier for this customer's account within a specific time frame. If the number of requests sent exceeds this limit, additional requests may be rejected by the carrier until the limit resets.

Recommended Action:

  1. Reach out to the carrier to verify the possibility of lifting the rate limit from their end for your account.

  2. Alternatively, if you want project44 to decrease the frequency of tracking update requests sent to this carrier for your shipments, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Carrier Blocking API Requests for Customer - Public Connection

Issue: project44 has surpassed the carrier's permitted limit for total calls to their public API for fetching shipment tracking information.

Recommended Action:

  1. project44 will continue to attempt to fetch data from the carrier and address the issue at hand.

  2. For a reliable long-term solution, it is recommended that you verify with the carrier if a private API access without rate limitations can be arranged for your account.

Carrier Blocking Website Data Access for Customer

Issue: project44 faced limitations in fetching tracking information from the carrier website due to access restrictions.

Additionally, the carrier has not provided project44 with a reliable API connection for accessing the customer's shipment tracking information. This could affect data consistency and completeness due to carrier limitations.

Recommended Action: You can enhance your data quality if your carrier establishes an API connection with project44.

  1. Submit a request to the carrier for an API connection.

  2. If the carrier has an existing API connection with project44 that is not enabled for your account, they can work with project44 to facilitate its setup.

  3. If the carrier does not have an API integration, they may need to develop a new one.

CTA: Request API Access

Related articles