Summary: A large order import can end with a 504 Gateway Time-out message even though the import is still running and the orders keep loading. Check the orders before you import the file again, and import smaller files.
Problem
You import an order file and get this message, and the upload window does not come back. The file is usually a big one, a few thousand rows:
504 Gateway Time-out (Source: Microsoft Azure Application Gateway v2)
Cause
The server that answers your browser only waits so long for a reply, roughly ten to fifteen minutes. A large import takes longer than that, so you get a 504 message.
The import itself is not cancelled. It keeps running in the background and the orders keep loading. The message is about the wait, not about the import failing.
How to check: wait a few minutes, then look for orders from that file in the orders list. If they are loading, the import is working.
Fix
- Do not import the same file again straight away. Re-uploading a file that already loaded replaces the items on those orders, so you can make things worse.
- Wait a few minutes, then spot-check several orders from the file and check they loaded.
- If the orders are there, treat the 504 message as cosmetic and carry on with your day.
- Import smaller files from now on so the import finishes inside the wait window. See "Batch import fails on a large file or reused shipment numbers" for how big a file can be.
- If orders from the file are missing once the loading stops, email support@shipstore.com with the file name, the time you imported it, and how many rows it had.
What you should see
Orders from the file appear in the orders list even though you saw the 504 message, and smaller files finish without it.
Related articles
- Batch import fails on a large file or reused shipment numbers
- Re-uploading an order file replaces the items, it does not merge them
- Large batches throw rating errors: use legacy mode