The Schedule Did Not Use My Second Shift: Where to Look

A second shift the scheduler seems to ignore is almost always one of three things: it is not assigned to the work center, it has no working hours on the days you expect, or the first shift already had enough capacity and the job never needed it. Each has a distinct check, and only the first two are anything to fix.

EDGEBIC by User Solutions allocates a job across the shifts a work center actually has, filling earlier windows first and spilling into later ones only when the work exceeds what the first can hold. This post covers a second shift that does not appear to be used; it sits in the EDGEBIC troubleshooting guide and pairs with how to add a second shift, shifts and calendars explained, and how EDGEBIC allocates hours across shifts.

First, Confirm the Work Center Can See the Shift

A work center only schedules against a shift it is connected to. There are two valid connections: the work center uses the plant-wide global shifts, or the specific shift is assigned to that work center directly. If the second shift is neither global nor assigned to this work center, the engine has no capacity windows for it and will never place work there. This is the single most common cause.

How to tell: open the work center's shift assignment and confirm either global shifts is on, or the second shift is listed. The anomaly report has a check for a work center that carries schedules but has no resolvable shift at all, which is the extreme case of this gap.

Fix: turn on global shifts for the work center, or assign the second shift to it directly through the work center's shifts tab. Then re-run scheduling so the engine can use the new window.

Cause 1: The Shift Has No Hours for Those Days

A shift only contributes capacity on days its daily hours are set. A second shift with a blank window on Tuesday adds nothing on Tuesday, even though it is assigned.

How to tell: the shift is assigned but its daily hours are empty or zero for the day-of-week the jobs run. The anomaly report and the scheduling failure message both call out a shift with no daily hours.

Fix: open the shift and set non-zero start and end times for every day-of-week it should run. Save, then re-run scheduling.

Cause 2: The First Shift Was Enough

The allocator fills earlier and immediately available shifts before spilling into later ones. A job whose hours fit inside the day shift completes there and never touches the second shift. That is correct behavior, not a fault. The engine ranks windows by how soon they are available and how much capacity they carry, so an open day shift beats a later night shift for the same work, and a job only reaches the night shift once the day shift on the days available cannot hold the remaining hours.

How to tell: the job's total hours are within what the first shift, times its instances, can hold on the days available. The second shift sits idle because the work was already placed.

Fix: none needed. If you specifically want the second shift used, the work has to exceed the first shift's capacity, or the first shift has to be constrained, before the engine reaches the later window. Adding work or reducing first-shift availability is a planning decision, not a repair.

Cause 3: The Shift Is Blocked or Inactive

An assigned shift with hours can still be unavailable on the target dates if it is inactive, sits under a shift holiday, or is consumed by downtime.

How to tell: the shift is inactive, or the anomaly report flags a booking on a shift holiday or inside a downtime window, or those calendar entries cover the days you expected the shift to work.

Fix: reactivate the shift, or remove or adjust the shift holiday or downtime that blocks the dates, then re-run scheduling.

The Reconciliation, in Order

1. Confirm the work center can see the shift: global shifts on, or the shift assigned directly.
2. Check the shift's daily hours for the specific days the jobs run.
3. Compare the job's hours to the first shift's capacity; a job that fits never spills.
4. Rule out inactive shifts, shift holidays, and downtime on the target dates.
5. Re-run scheduling after any assignment or calendar change so the engine uses the corrected windows.

Prevention

• Assign every shift a work center should use, or set the work center to global shifts, at setup time rather than after a schedule looks wrong.
• Fill the daily hours for every working day on each shift, so no day silently contributes zero.
• Expect spill, not splitting. Shifts fill in priority order; a job using only the first shift is efficient, not broken.
• Re-run scheduling after calendar edits. A newly assigned shift does not change an existing plan until the next run.
• Check the load view before assuming a fault. A work center that finishes its work on the first shift shows the second shift idle, which is the efficient outcome, not a shift the engine failed to use.

If capacity reads zero for the work center entirely, that is a broader gap covered in capacity shows zero for a work center, and a calendar closure that behaved unexpectedly is covered in a holiday did not reduce capacity. The full model is in multi-shift scheduling explained.