A Veracore order load can run very slowly and fail with "The request channel timed out while waiting for a reply." The host (Veracore) is timing out, not Shipstore. A label can still generate on the attempt that times out, so check Shipment History before you retry, and have the host clear the slowdown.

Problem

The system is very slow and you get timeout errors, sometimes needing several tries before a label prints. The logs show:

Exception getting Order details for order [order number] from Veracore. The request channel timed out while waiting for a reply after 00:00:59.

On some attempts the label is actually created despite the timeout, and reprocessing then says the shipment has already been shipped.

Cause

The timeout happens when Shipstore's request to the host (Veracore) for order details does not come back within the time window. The cause is the host being slow or down, not a Shipstore setting. Because the label can be created on the attempt that times out, a blind retry can make a duplicate-shipment error. If it affects several stations or users at once, it points to the host, not one workstation.

Fix

  1. Confirm the error names the host (Veracore) and reads "The request channel timed out while waiting for a reply."
  2. Before you retry a timed-out shipment, check Shipment History for that order. If a label already generated, do not reprocess. That is why a retry says the shipment has already been shipped.
  3. If it affects several stations or users, treat it as a host-side slowdown and open a ticket with Veracore support, since the delay is on their side.
  4. Retry processing once the host confirms the issue is resolved.
  5. If Shipstore shows the requests leaving promptly but the host not replying, capture an example order number and the time, and email support@shipstore.com with your company name so support can review it with the host team.

What you should see

  • Labels generate without a timeout once the host is responsive.
  • No duplicate shipments from retries, because you check Shipment History before reprocessing.

Related articles

  • Host error while processing: message queue allocated to another job