Summary: On a self-hosted server, automated imports use the File Watcher service and batches use the Batch Processing service. After a reboot or power outage either can be left stopped. Restart it and set both to start with Windows.

Problem

Files stop importing automatically, or batches stop processing (a Processing window stays open while nothing happens, sometimes with no error and no logs). This often starts after a server reboot, Windows update, or power outage.

Cause

On a self-hosted (Private or Enterprise) server, automated import needs the Shipstore File Watcher service running, and batches need the Shipstore Batch Processing service running. After a reboot or power event, one or both can be left Stopped, so nothing imports or processes until the service is started again. Shipstore cannot monitor a server you host.

How to check: On the server, open the Windows Services list and see whether the Shipstore File Watcher and Batch Processing services show Running.

Fix

  1. On the server, open the Windows Services list.
  2. Find the Shipstore File Watcher service. If it is stopped, start (or restart) it.
  3. Find the Shipstore Batch Processing service. If it is stopped, start (or restart) it.
  4. Set both services to start automatically with Windows so a reboot does not leave them stopped.
  5. Because Shipstore cannot monitor a server you host, set up your own monitoring to alert your IT team when either service stops, and have IT check both after any reboot, Windows update, or power event.
  6. If a batch keeps loading and never processes on a hosted (Public Cloud) account, email support@shipstore.com with your company name so we can restart the backend service, then re-run the batch.

What you should see

Both the File Watcher and Batch Processing services show Running. Files placed for import are picked up automatically, and queued batches rate and ship.

Related articles

  • Emailed report stops arriving after a column change
  • Batch stays In Process and never rates or ships