FAQ¶
Quick answers to what dispatch asks most.
Why didn't my order route?¶
It'll be in the Unrouted list with a reason. The common ones:
UNDER_MIN_WEIGHT— the group is below the truck minimum. Atlas won't ship under the minimum; combine it with more work or force it through knowingly.COIL_EXCEEDS_TRAILER— a single coil is too heavy for the trailer.EXCEEDS_DRIVE_TIME— driving plus stops is over the truck's limit.
See Routing → Read the results.
Someone else is already routing — why can't I run?¶
Atlas allows one routing run at a time across the whole team, on purpose, so two people can't route the same orders into different trucks. Wait for the run in progress to finish; the board updates when it does.
The board looks stale. What do I do?¶
Check the sync countdown in the header. If it says anything other than Just now, press Sync now and wait for the refresh. Always sync before routing.
A load moved to "Locked" — did I do something wrong?¶
No. A load locks when a fresh sync changes one of its orders after it was approved. Open it, read the conflict, and either re-route or accept it. See Loadouts → Locked loadouts.
Can I delete a loadout?¶
No — loads are approved or rejected, never deleted. Rejecting sends the orders back to be routed again and keeps the history intact.
Does changing my department hide other teams' work?¶
No. Department is an audit stamp — it records who ran a job. It doesn't filter the board. Set it to match the crew doing the work.
Why does the coil count look different from what I expected?¶
Atlas counts coils on the server and de-duplicates a produced coil against its original planned lot, so the same steel isn't counted twice. If a number still looks off, note the load and raise it with dispatch.
Missing an answer?
This FAQ is a starting point. Add the questions your team actually asks — that's what makes it useful.