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

Search

search shadow

Articles in this section

FTL No Tracking Methods Errors and Recommended Actions

Rich Hellinga
Rich Hellinga
Updated

In this article

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

Root Cause Error

Recommended Action

No Vehicle Found for Given Equipment Identifier

Issue: project44 was unable to identify a vehicle corresponding to the specified equipment identifier.

Recommended Action:

  1. Contact the carrier to verify whether the provided equipment identifier is accurate and active.

  2. If you wish to remove equipment identifier validation during the shipment creation process, please contact your project44 CSM.

  3. If the problem persists or if you need additional help, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Missing Equipment Identifier

Issue: project44 could not track the shipment because no equipment identifiers were provided.

Recommended Action:

  1. Provide the appropriate equipment identifiers to enable shipment tracking with project44.

  2. If the shipment is expected to track via API, contact your carrier and request them to add the required push configuration.

  3. If the shipment is expected to track via the DriveView app, provide the mobile number associated with the driver.

  4. If the problem persists or if you need additional help, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Carrier Does Not Have Configured Tracking Methods

Issue: The carrier has not configured any shipment tracking methods, such as API or Telematics, with project44. Configuring tracking methods is necessary for shipment tracking.

Recommended Action:

  1. To enable Telematics as an available tracking method, the carrier should log into the Network Management Center (https://nmc-na12.voc.project44.com/ or https://nmc-eu12.voc.project44.com/) and add their Telematics connection by following the on-screen guide.

  2. Reach out to project44 support via this link and raise a "Carrier Integration Request" ticket for additional assistance.

Invalid Equipment Identifier

Issue: project44 could not track the shipment because we were unable to validate the provided equipment identifier.

Recommended Action:

  1. Verify that the provided equipment identifier is registered with project44.

  2. Ensure that the equipment identifier provided to project44 matches the equipment identifier registered with the Telematics provider. This is crucial to ensure correctness and alignment across the board. Instructions on obtaining the identifier for the most commonly used providers can be found here.

  3. If the problem persists or if you need additional help, 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, kindly reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

DriveView - Missing Phone Number

Issue: The carrier has previously tracked using the DriveView app, but currently, they do not have any other tracking methods configured with project44.

Recommended Action:

  1. Provide a valid phone number as the equipment identifier if you expect this shipment to track via the DriveView app.

  2. If you want to configure additional tracking methods for this carrier, contact the carrier and request them to add new tracking methods with project44.

  3. To add new tracking methods, the carrier should log into the Network Management Center (https://nmc-na12.voc.project44.com/ or https://nmc-eu12.voc.project44.com/) and add their connection by following the on-screen guide.

  4. Reach out to project44 support via this link and raise a "Carrier Integration Request" ticket for additional assistance.

DriveView - Invalid Phone Number Assigned to Shipment

Issue: The shipment was assigned an invalid phone number as its equipment identifier. It is essential to set a valid mobile number, including the '+' sign and country code, to be able to track via the DriveView app.

Recommended Action:

  1. You are requested to ensure that the phone number used for the shipment correctly corresponds to the driver who will be carrying the shipment and is including the '+' sign and country code.

  2. Correspondingly, drivers can assign shipments to themselves using Driver Initiated Shipments feature on the DriveView app.

  3. If the problem persists or if you need additional help, kindly reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Carrier Not Assigned to Shipment

Issue: This shipment does not have a valid carrier identifier assigned to it.

Recommended Action:

  1. Validate that the specified carrier identifier was a part of the Implementation Scope or Statement of Work (SOW) outlined in the contract.

  2. Verify that the correct carrier identifier has been provided in the shipment creation request.

  3. If both validations are successful, kindly reach out to project44 support via this link and raise a "Carrier Integration Request" ticket for additional assistance.

Shipment Initialization Failed for Provided Tracking Method

Issue: The shipment could not be initialized for the selected tracking method.

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.

Equipment Identifier Type Mismatch

Issue: The provided identifiers do not match the expected identifier type for the carrier. Equipment identifiers are required during shipment creation or can be updated afterward.

Dynamic: The shipper has provided the following identifiers: {{providedIdentifiers}}, while the carrier is expecting identifiers: {{expectedIdentifiers}}.

Recommended Action:

  1. Verify that the provided identifiers match the expected identifiers from the carrier. You can find a list of expected identifiers by carrier by following the instructions outlined in this project44 support documentation.

  2. If the problem persists or if you need additional help, reach out to project44 support via this link and raise a "Support Request" ticket for assistance in resolving the matter.

Dynamic: For any future shipment with this carrier, please ensure to provide at least one of these identifiers upon creation: {{expectedIdentifiers}}.

Shipment Created after Delivery

Issue: The shipment was created after the delivery window had elapsed. Initiating shipments after their physical transit shall result in tracking being missed.

Recommended Action: Review the affected shipments to understand why the creation occurred after the delivery window, and kindly revise the operational flow to prevent recurrence.

No Tracking History Available for Carrier

Issue: The carrier has never successfully tracked a shipment in the project44 network, indicating that their onboarding process was not completed successfully.

Recommended Action:

  1. Please confirm the invitation status for the carrier in the Network Management Center (https://nmc-na12.voc.project44.com/ or https://nmc-eu12.voc.project44.com/).

  2. If no invitation exists, you are requested to send a new invitation.

  3. If the carrier is already invited, validate the carrier contact information used in the Network Management Center via email outreach. Resend the invite with the confirmed valid contact information.

  4. Reach out to project44 support via this link and raise a "Carrier Integration Request" ticket for additional assistance.

Failed to Determine Tracking Method for the Shipment

Issue: Despite having valid equipment identifiers, no tracking method could be applied to the shipment by project44.

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.

Related articles