Staff not working: separate idle, blocked and stuck employees

Find the first point where a job stops

1. Confirm the worker is assigned here and currently on shift.
2. Confirm the needed role is assigned.
3. For a cook, expand the recipe for missing ingredients or processors.
4. For serving, distinguish no new order from food already prepared but undelivered.
5. For cleaning, identify actual cleanup work rather than an empty venue.
6. Watch whether another eligible task is being completed before concluding the employee is stuck.

Use the dated task order carefully

Update 2 documents serving, processing and making food before taking a new order; manager work follows, with cleanup later. It encourages specialization rather than expecting one worker to cover a large venue.

That dated order explains why a lower-priority job can wait. It does not prove your save’s active task, and it does not make every employee eligible for management or cleaning. If an ingredient is absent, solve the recipe requirement before adding staff.

Match a continuing report to the current build

Update 2 suggested reducing hired staff as a workaround for an investigated idle-position issue. Update 4 later fixes some characters walking in circles or appearing inside furniture at idle spots. The old workaround remains historical advice, not a reason to fire employees as the first diagnosis.

If a valid job and all requirements are present but no action follows, record the build, venue, worker, shift, role, recipe, visible obstruction and before/after behavior. Success is that the specific job resumes; otherwise keep the case unresolved. For purchasing failures, use the separate manager checks.