This article explains the automated frequency at which the techTRACK's Tracking Monitor queries Carriers for shipment status updates.


techTRACK utilizes a smart polling logic designed to optimize tracking updates based on shipment activity. This system automatically adjusts how often it checks for new events depending on the stage of the shipment lifecycle.


This article is divided into the following sections:

  1. Standard Polling Logic
  2. Lifecycle-Specific Frequencies
  3.  Monitoring Expiration


I. STANDARD POLLING LOGIC


To ensure efficient monitoring, techTRACK uses a dynamic time scale to check for updates. The frequency of checks depends on the time elapsed since the last successfully captured event:

  • Initial Interval: The system checks for updates every 3 hours.
  • Incremental Backoff: If no new tracking events are received, the time between checks increases incrementally from 3 hours, to 6 hours, to 12 hours, and finally to 24 hours.
  • Activity Reset: Once a new event is successfully received from the Carrier, the frequency automatically rolls back to the initial 3-hour interval.


II. LIFECYCLE-SPECIFIC FREQUENCIES


Specific stages of a shipment's lifecycle trigger different monitoring behaviors to prioritize relevant data capture:

  • New Shipments (First 24 Hours):
    Regardless of the standard logic, for the first 24 hours after a tracking number is created, techTRACK checks for updates every 3 hours until an induction scan (confirmation of receipt by the Carrier) is detected.
     
  • Delivered Shipments:
    After a package status is updated to "Completed" the system continues to check the status every 24 hours for a period of 7 days to capture any potential post-delivery updates or corrections.


III. MONITORING EXPIRATION


To maintain system performance, techTRACK will stop checking for new events 30 days after the tracking number was created.

 

NOTE: If you suspect a tracking number is not updating correctly within these timeframes, please refer to the guide: How to View Last Tracking Synchronization Error Details [Step-by-Step Guide].