Tracking Failed Events

When Master Bills and containers fail to track, you can receive two events via webhook:

1. shipment.tracking.failed for when an MBL is not found
2. container.tracking.failed for when a container is not found on a valid MBL

How does the tracking process work?

When OpenTrack receives a tracking request, it will make up to 200 attempts to locate the shipment over the course of two weeks at logarithmically decreasing intervals (i.e. very often at first, then somewhat less often, then even less often). During this time, the container's status will be DISCOVERING.

When does tracking fail?

If OpenTrack cannot locate the container within those two weeks, then the tracking.failed events are triggered. The container's status then moves to NOT_FOUND.

Here is a sample payload for each one:

shipment.tracking.failed

{
  "body": {
    "event": "shipment.tracking.failed",
    "data": {
      "shipment": {
        "number": "MBOL7326991000",
        "referenceNumbers": [
          {
            "name": "assigneeId",
            "value": "ID123456"
          }
        ]
      },
      "trackingAttempts": 131,
      "attemptsRemaining": 69,
      "account": {
        "region": null,
        "domain": "yourdomain.com"
      }
    },
    "deliveryAttempt": 1,
    "pendingRetries": 4,
    "sentAt": "2023-10-04T09:41:14.466Z"
  }
}

container.tracking.failed

{
  "body": {
    "event": "container.tracking.failed",
    "data": {
      "container": {
        "containerId": "CNTN4936320",
        "masterBill": {
          "number": "MBOL1230962361",
          "referenceNumbers": []
        }
      },
      "account": {
        "region": null,
        "domain": "yourdomain.com"
      }
    },
    "deliveryAttempt": 1,
    "pendingRetries": 4,
    "sentAt": "2023-11-07T13:00:11.267Z"
  }
}