Menu
Home OceanIO Use cases Start a container tracking Handling 'No Data Available'

Handling 'No Data Available'

When a Container Tracking request is created, tracking information may not always be available immediately.

This can happen, for example, when:

  • The carrier has not yet provided tracking information.
  • The container, Bill of Lading (BL), or booking has not yet been registered by the carrier.
  • The provided Container, BL, or booking reference does not exist or cannot be identified.

To account for situations where data becomes available after the initial request, the Container Tracking platform automatically retries the data request according to a predefined schedule.

The retry strategy depends on whether a SCAC code is provided as part of the tracking request.

Container Tracking Request with SCAC

When the SCAC code is provided, the platform knows which carrier to query and can continue checking for tracking information over an extended period.

The following retry logic is applied:

  • 1st request: Immediately after the initial POST request.
  • 2nd request: 10 minutes after the initial POST request.
  • Next 8 requests: Every 8 hours.

This results in a total of 10 data requests during approximately the first 64 hours.

If tracking information is still unavailable after this period, the platform changes to a longer retry interval:

  • A new data request is made every 72 hours.
  • Up to 20 additional requests are performed.

In total, the platform may continue requesting tracking information for approximately 63 days from the initial POST request.

This extended retry period is intended to handle cases where a valid shipment has been created, but the carrier has not yet made the tracking information available.

Illustration of No data handling for Container Tracking.

Tracking Request without SCAC

When SCAC code is not provided, the platform applies the same retry strategy during the initial period:

  • 1st request: Immediately after the initial POST request.
  • 2nd request: 10 minutes after the initial POST request.
  • Next 8 requests: Every 8 hours.

This results in a total of 10 data requests during approximately the first 64 hours.

If no tracking information has been identified after this period, the platform continues checking:

  • A new data request is made every 72 hours.
  • The retry process continues until 14 days have passed since the initial POST request.

The shorter retry period reflects the additional uncertainty when the carrier is not explicitly identified through a SCAC code.

Illustration of no data handling for Container Tracks without SCAC

Updated on 07 September, 2026