Worker Won't Start? Fix the Node Job in Five Checks

Do not start by firing the worker or withdrawing random nodes. Check the chain in order, because each step rules out a whole class of failures.

• Investment: the main node and the actual production subnode are active.
• Route: the worker's home town can reach the job through connected nodes.
• Stamina: the worker has enough stamina and is not tied up on another job.
• Storage: confirm the worker's configured output destination and leave room for all materials and byproducts. Workers can use Delivery from level 1 to send production-node output to a selected town storage.
• Materials: workshop ingredients are in the worker's home-town storage, not merely somewhere in the Family.

Open the World Map and use Production Node Information. The March 26, 2026 update added this tab plus clearer worker destinations. In that official UI wording, a deactivated entry can mean the node is active but has no worker assigned, while an activated entry has a worker assigned—so read the status detail instead of assuming the color means your Contribution Points vanished.

The Worker List can jump to a working node, and the map can show a worker's destination. If the destination is wrong, cancel the wrong assignment deliberately; if no destination appears, continue down the checklist.

A discovered node is not the same thing as an invested production chain. Confirm the main node, open its production branch, and invest in the exact lumbering, mining, farming, or other subnode you want. Then trace a continuous invested route back to the town where that worker was hired.

Use the live Contribution Point values shown on your map. The June 4 patch reduced costs in many places and changed or added production nodes, so an older spreadsheet can send you toward a route that no longer matches the client.

Open the Worker List and check the worker's current task and stamina. Feed the worker if stamina is empty, or use the current Fully Recover Stamina control when that is the cleanest way to refill the roster. Do not assume a worker displayed in the list is idle; verify the destination and remaining job time.

If a recovered, idle worker still cannot be selected, return to the route and subnode checks. Rehiring is a last move, not a first fix.

For a production-node job, check the storage destination configured for that worker. Delivery is available from level 1 and lets you choose the town storage for harvested output. Leave space for every expected item type, then run one cycle and confirm where the output lands.

Clear or move a few stacks, restart a single cycle, and watch where the output lands. That small test proves the storage path before you queue a large repeat count.

A production node gathers from the destination, but a workshop consumes materials. Put every required workshop ingredient in the storage of the town that owns the worker. Materials in another city, Central Market Warehouse, character inventory, or a different storage do not prove the job can start.

Select the recipe again after moving the materials and confirm the displayed worker and origin town. This catches the classic setup where the workshop house is correct but the chosen worker belongs somewhere else.

The April World Map update added integrated search for node names, products, NPCs, and functions. Use it to locate the exact product instead of navigating from memory. Production nodes changed in June, and Inner Edania received new one-CP nodes and production branches in August.

Use the current World Map values and effective NA/EU PC updates when a route differs from an older screenshot. A Global Lab preview does not override the live network.

After the fix, run one job cycle and verify the worker destination, stamina use, timer, and returned output before selecting repeat forever.

• The production subnode shows an assigned worker.
• The chosen worker's home town is the one you intended.
• The route remains connected after all Contribution Point changes.
• The selected output storage has spare slots and receives the result.
• Only after that proof should you increase repeat count or expand the network.