techOMS integrates seamlessly with techSHIP to automate rate shopping and shipment processing, saving you time and reducing manual data entry in your daily warehouse operations.
This article explains the retry policies that apply when the system encounters connection errors during data retrieval operations.
![]() | To initially configure this connection, refer to How to Manage Account Warehouses and Fulfillment Channels [Step-by-Step Guide]. | |
| | ||
TABLE OF CONTENTS
Retry Trigger Conditions
techOMS uses an automated retry policy that activates specifically when communication interruptions occur between the system and techSHIP.
The retry policy is triggered exclusively by the following error conditions:
- Cannot get data from techSHIP.
- A techSHIP timeout occurs during the request.
- A connection timeout expires because all pooled connections are currently in use.
Scope of Application
This retry policy applies to two main fulfillment areas within your techOMS environment:
- The automated Calculate Time & Transit (TNT) action configured within a Sales Order Rule. For setup instructions, refer to How to Use the Calculate Time & Transit (TNT) Action [Guide].

When executing the TNT action, the retry policy applies only to active and enabled Fulfillment Channels. If some carriers return valid data while others return an error unrelated to connection issues (e.g., an invalid zip code), techOMS skips the retry policy and successfully uses the valid carrier data for that specific location. - The manual Estimate action triggered during the Rates step of the Packing Module wizard. To learn more about this workflow, refer to Understanding the techOMS Packing Module [Information].
Retry Policy Execution
Once triggered, the automated retry system follows a specific sequence to ensure the highest possible success rate for your shipments.
- Retry Attempts: techOMS will attempt to retrieve the required data up to four additional times, resulting in a maximum of five total attempts.
- Retry Intervals: To allow external connections to stabilize, the retry attempts occur at increasing intervals: 5 seconds, 30 seconds, 60 seconds (1 minute), and 180 seconds (3 minutes).
- Failure Conditions:If the data cannot be retrieved after all five attempts, the system handles the failure based on the originating action:
- TNT Action: The request is moved to a failure queue. The entire order is marked as failed, and you must perform manual intervention. You can review the exact execution and retry details within the Sales Order Log. For instructions, refer to How to review the Sales Orders Log [Step-by-Step Guide].
- Packing Module: During the Rates step, the system will display an error notification. No shipment is created automatically, and the Processing Log will record the specific error returned by the techSHIP carrier. You must then manually select your desired Carrier and Service to proceed to the Shipping step.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article