An assigned worker who is standing still is not enough evidence of a broken AI. In Dirty Business, the worker panel reports the next thing that job is waiting for. Read that live reason before replacing the employee, rebuilding the room, or buying another machine. Most stalls are a dependency problem: the process is still running, the correct material is not on a Supply Rack, a required station is unavailable, the finished product has nowhere to go, or the task queue is empty.
The reliable fix is a short loop: read one idle reason, change only the resource named by it, then reopen the worker panel. That last check matters because clearing an input shortage may expose a machine shortage, and freeing the machine may expose a full output rack. This guide traces that loop through Botanical Engineers, Weapons Technicians, Lab Operators, and Counterfeit Experts without inventing production times, optimal staff counts, or permanent Early Access balance.
Start with the reason that is true right now
Open the affected worker’s panel and copy the current idle reason exactly. Do not begin by moving every station or restocking every shelf. The message tells you which layer of the chain deserves attention, and each layer has a different repair.
| Panel state | What it means | First action | Wrong first response |
|---|---|---|---|
| A named process is waiting | The worker has already started a timed step | Watch the named machine or biological process finish | Canceling the job or hiring another worker |
| A supply is missing | The assigned recipe cannot draw its next matching input from a Supply Rack | Put the exact named material on a Supply Rack | Dropping it on the floor or carrying it in personal inventory |
| No named equipment is available | The station is absent, occupied, or still boxed | Find that station and determine which of those three states applies | Adding more input stock |
| No Product Rack is available | Completed output has no delivery slot | Clear or add Worker Product Rack capacity | Buying another upstream machine |
| No Tasks Assigned | The worker has no queued job | Assign the intended task in the Staffing Hub | Treating the empty queue as pathfinding failure |
After the smallest relevant change, return to the same panel. If the reason disappears and the worker moves, the diagnosis was correct. If a different reason replaces it, continue from the new message rather than repeating the first repair. If the same reason remains, verify that the item or machine you changed is the one named by the assigned task.
Do not repair a timer
Four launch-build messages describe work that is already in progress: Waiting For The Plant To Grow, Waiting For Weapon Printer, Waiting For Distiller / Slug Extracts, and Waiting For Banknote Printer / Drying Machine. These are not equivalent to an empty task queue. The employee has reached a step that another process must finish.
Check the named object before intervening. If the plant, printer, distiller, slug process, or drying machine is visibly active, let that stage complete and preserve the assignment. A second employee cannot make one occupied station complete two jobs at once. Reassigning the first worker can instead hide the useful evidence by replacing a normal wait with a new queue or supply problem.
There is no verified universal wait time in this evidence set, so this guide does not attach minutes to those labels. Use completion as the breakpoint. Once the named process finishes, reopen the panel. Continued idling should produce the next actionable reason; if the interface never advances despite a completed process, capture the current status and build version before reporting a bug.
Match the rack to the assigned recipe
The launch guide makes a strict distinction between owning an item and making it available to automation. Workers draw their inputs from Supply Racks. A material in your personal inventory or lying on the floor does not satisfy that dependency. Put one exact missing input on the designated rack, then check the panel again.
The word matching is as important as the item category. A Weapons Technician asking for a particular filament will not use a different filament simply because both are stored nearby. The same rule applies to seeds, slugs, and printer cartridges. When one task works and another task at the same department does not, compare the assigned variant with the rack contents before changing the room layout.
Packaging and support items can stop a line just as decisively as the primary material. A Botanical Engineer may be waiting for soil, the correct seed, a filled watering can, or plastic packs. A Lab Operator may need the matching slug, slug food, or blotting paper. A Counterfeit Expert can stop for blank paper even when the correct cartridge is present. Restock against the full panel message, not against what the finished product looks like.
Trace each specialist from input to output
Use the following map as a diagnostic index, not as a purchase order. It records the role-specific dependencies named by the launch guide. It does not prove that every item is needed simultaneously or that the list will remain unchanged through Early Access.
| Worker role | Normal waiting state | Supply Rack checks | Equipment availability checks |
|---|---|---|---|
| Botanical Engineer | Plant growth | Soil Packs; matching Seeds; Watering Can With Water; Plastic Packs | Weed Pot; Weed Bud Basket; Weed Bud Packing Table |
| Weapons Technician | Weapon Printer | Matching Filaments | Weapon Printer; Workbench |
| Lab Operator | Distiller or Slug Extracts | Matching Slugs; Slug Food; Blotting Paper | Slug Tank; Distiller; Dropper |
| Counterfeit Expert | Banknote Printer or Drying Machine | Blank Paper Sheets; matching Printer Cartridges | Banknote Printer; Guillotine Cutter; Drying Machine |
Read across one row in production order. For example, a Counterfeit Expert can have the correct task and paper yet still wait because the matching cartridge is absent. After both inputs are available, the same line can pause normally at the printer, then fail at the cutter or dryer if that station is missing or occupied. Finally, it can block at delivery when there is no Worker Product Rack capacity. Fixing “the counterfeiting room” is too broad; fix the exact edge between the last completed step and the next one.
Available equipment has three separate tests
When the panel says there is no available Weed Pot, Workbench, Distiller, Guillotine Cutter, or another named station, inspect that specific object in three passes:
- Does it exist? If the required station was never acquired or placed, the task has nowhere to run. Confirm the assigned line before buying equipment.
- Is it unpacked and usable? A machine that is still inside its delivery box is not available to the worker. Unbox it and return to the panel.
- Is another job holding it? An existing station may be operating for another employee or batch. Wait for the active step or add capacity only when repeated contention, not a one-time wait, proves that the station is the bottleneck.
This order prevents the most expensive misdiagnosis: adding payroll to a line that has only one usable machine. More workers increase demand on the same station. They do not create another printer, table, tank, cutter, or dropper.
A full Product Rack blocks the finished end of the line
No Available Product Rack means the difficult work may already be complete. The employee is holding output but has no valid place to deliver it. Clear finished goods from the Worker Product Rack or add rack capacity, then reread the status. Feeding more raw material into this line increases pressure without creating an exit.
This is back-pressure, so diagnose it from the end toward the beginning. First make a destination available. Then let the worker deposit the completed item. Only after that should you judge whether inputs or machine throughput are too low. If several otherwise healthy lines converge on full racks, the shared output capacity is the constraint; rebuilding each production room would attack the wrong layer.
An empty queue is fixed in the Staffing Hub
No Tasks Assigned is the simplest message and the easiest to overcomplicate. Open the Staffing Hub and place the intended work in that employee’s task queue. Then verify that the new task is the correct product or variant before stocking supplies for it.
Assignment is only the first dependency. A valid queue can immediately reveal a missing matching input, and supplying that input can reveal an unavailable station. That sequence is useful: it proves the worker is evaluating the line. Do not treat the appearance of a second reason as failure of the first fix.
Let the second idle reason identify the real choke point
A productive troubleshooting session often ends with two or three different messages. Suppose a Botanical Engineer first asks for matching Seeds. After the correct seeds reach a Supply Rack, the panel changes to no available Weed Pot. Unboxing a pot then exposes no available Product Rack. The original seed warning was real, but the final output destination was the constraint that would have stopped the batch later.
Use a one-change ledger when the room is complicated:
- Record the exact status and worker role.
- Change one named dependency.
- Reopen the panel and record the replacement status.
- Stop only when the worker resumes, reaches a normal waiting process, or produces a repeatable state that survives a current-build recheck.
This preserves the difference between a broken chain and a possible bug. A bug report that includes the role, task, last completed step, live idle reason, rack contents, machine state, output capacity, and build version is more actionable than “workers do nothing.” The official launch feed was already receiving hotfixes, so confirm the current client before relying on an older workaround.
Scale the blocked resource, not the headcount
Before hiring again, watch which reason repeats across completed cycles. If workers repeatedly wait for matching inputs while machines sit unused, increase the reliability of that Supply Rack. If valid jobs repeatedly queue behind one active printer or distiller while inputs and output space remain available, machine capacity is the candidate constraint. If finished goods repeatedly stop at delivery, expand or clear Worker Product Racks.
Only add another worker when the existing chain has enough matching supplies, usable equipment, and output space to give that person work. The evidence does not establish one best staffing ratio or a permanent profit-per-worker calculation, and launch balance can change. The safer expansion rule is observable: buy the resource named by a recurring status, not the resource that merely looks busy.
In the official four-player co-op mode, give one player temporary ownership of the dependency check while the others continue production or deliveries. That player reads the worker panel, names the exact missing item or station, and confirms the new status after the change. One owner prevents teammates from simultaneously moving equipment, restocking the wrong variant, and clearing the task queue, which would erase the cause before anyone verifies it.
Sources & credits
- Dirty Business on Steam — current AppID, developer/publisher, Early Access release state, official feature scope, co-op support, and original screenshots.
- Official Steam announcements — launch confirmation, hireable staff as a post-demo system, four-player boundary, and current hotfix context.
- Workers Not Working Solution — launch-day community guide used for the exact panel states and role-specific dependency names. Direct HTTP returned 429; the readable browser recovery was preserved separately, and its rules are not presented as permanent developer documentation.
The supplied fan wiki was readable and useful for locating the worker topic, but it identifies itself as unofficial and its broader staffing recommendations could not be verified against current first-party material. Those claims were excluded. Both article images are untouched 1920×1080 official Steam JPGs; no competitor artwork, AI-generated image, or video embed is used.