When a Container Tracking request is created, tracking information may not always be available immediately.
This can happen, for example, when:
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.
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:
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:
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.

When SCAC code is not provided, the platform applies the same retry strategy during the initial period:
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:
The shorter retry period reflects the additional uncertainty when the carrier is not explicitly identified through a SCAC code.
