Quick answer
When Fetcher icons disappear or a route stops updating, inspect the connection and warehouse rules first, then save and reload once. Separate a UI display problem from a worker who is genuinely idle or blocked.
Version and source notesUpdated 2026-09-05 · Current for this version
- Updated
- 2026-09-05
- Works with
- PC Fetcher UI, routes, and warehouse connections
- What this guide covers
- UI symptom separated from genuine worker and input failures
- Version notes
- Fetcher icons and pathfinding may change with updates
- Update status
- Current for this version
Diagnosis order
- Select the source, destination, and warehouse to confirm the route still exists.
- Check storage permissions, input/output slots, camp range, and available workers.
- Pause and resume the route or rebuild only the affected connection.
- Save, reload, and compare the icon with actual stock movement.
- Record whether goods move despite the missing icon before reporting a bug.
What the icon does not prove
A missing icon does not always mean a missing Fetcher. The worker may be moving goods while the UI fails to refresh, or the route may be valid but starved of input.
FAQ
Should I reassign every Fetcher?
No. Test one route first; a global reassignment can hide the original bottleneck.
Is a reload a permanent fix?
It is a diagnostic step, not a guarantee. Keep the build and route details if the symptom returns.
Next step
Use Fetcher logistics, warehouse logistics, and production chains for deeper bottlenecks.