Truckload Notifications FAQs
If you are configured to receive all tracking updates, project44 will push an update every time there is a change to the position of the truck or the latestStatusUpdate
has changed. This means it is possible to get two updates in a row that have the latestStatusUpdate
with same statusCode
.
For example,
-
You could receive this notification, which shows the most recent
statusCode
of the shipment and the geo-coordinates of the truck."latestStatusUpdate": { "timestamp": "2023-12-12T00:48:02-0500", "statusCode": "AT_STOP", "geoCoordinates": { "latitude": 39.656254, "longitude": -84.61627 },
-
Then receive this following notification with the same
statusCode
as above but shows the truck's new geo-coordinates."latestStatusUpdate": { "timestamp": "2023-12-12T00:58:02-0500", "statusCode": "AT_STOP", "geoCoordinates": { "latitude": 39.67231, "longitude": -84.61628 },
Why do I see status updates on my shipments in the UI but never received them in the notifications to my web hook?
This is likely due to status updates that were received out of order or for updates that happened before the shipment was created. To verify, check time timestamp of the most recently received update. If this timestamp is earlier than any of the other status timestamps, project44 will not push it in the latestStatusUpdates
portion of the notification. If you want to see all status updates, contact your project44 Technical contact to enable the necessary configuration.
This occurs when project44 receives an update from the Carrier and the lastStatusUpdate
does not change. Any newly received updates will be in the statusUpdate
section of the payload. However, despite project44's best efforts to eliminate duplicate messages, the asynchronous nature of project44's platform makes it is impossible to guarantee uniqueness.
Are out of order updates still accounted for even though they do not trigger Truckload Notifications?
Yes. project44 does not throw away any data the Carrier sends because all data adds to the complete picture of the shipment. While Out of Order Events do not trigger a Truckload Notification, information about these events can be found in Movement and the VOC.
Look at the shipment APIs and see if there are events that occur with timestamps before the DISPATCHED
event.
For example, you can find any historical backfill events in events
array of the Get full tracking history API (Unified), in the statusUpdates
array of either the Get status of a truckload shipment by shipment identifier API or the Get status of a truckload shipment by unique system ID API (Truckload), or in the shipment details page available through Movement or the Visibility Operations Center.