Sync from Invex¶
For dispatch · keeping the board fresh
Atlas doesn't hold its own copy of your orders — it pulls candidate orders from Invex and keeps them in step. Syncing is how new and changed work reaches the board.
When sync happens¶
- Automatically, on a schedule. A countdown in the header shows how long until the next pull.
- Manually, whenever you press Sync now — useful right after someone releases a batch of orders in Invex.
Either way the sync runs in the background. You can keep working; the board refreshes on its own when the run finishes and a short "synced" toast appears.
sequenceDiagram
participant You
participant Atlas
participant Invex
You->>Atlas: Sync now
Atlas->>Invex: fetch candidate orders
Invex-->>Atlas: orders + tags
Atlas->>Atlas: match tags → materials
Atlas-->>You: board refreshed
Reading the countdown¶
| Countdown shows | Meaning |
|---|---|
A timer (e.g. 4:12) |
Time until the next automatic sync. |
| Syncing… | A run is in progress — the board is about to update. |
| Just now | The board reflects the latest Invex data. |
Sync before you route
A routing run only sees what's on the board at launch. If someone just released orders, press Sync now and wait for the refresh before routing, so nothing gets left behind.
What a sync changes¶
- New orders appear as routing candidates.
- Updated orders (quantity, ship-to, dates) are refreshed in place.
- Produced coils are matched back to their job so they aren't double-counted against what was still planned.
A sync can conflict with an approved loadout
If an order that's already sitting in an approved load changes in Invex, that load moves to the Locked lane so someone can review it before it ships. See Loadouts → Locked loadouts.