A new Release to Production modal lets you choose exactly where a job lands on the production board — append it to the end of the queue or insert it at a specific date. Before committing, you can preview how the release will affect existing work order schedules and spot any jobs that would become late.
The scheduling engine now sequences operations based on each machine's queue position, ensuring work is dispatched in the order you've arranged it on the board rather than arbitrarily.
Jobs that haven't been released to production are now excluded from machine capacity calculations, giving you a more accurate picture of available capacity and more realistic delivery estimates.
Cancelling a drag now correctly reverts the card to its original position. The drag placeholder also resizes accurately based on the card's size at the moment dragging begins.
Cards blocked by an unfinished upstream operation now display a visual indicator so operators can immediately see why work hasn't started.
If a server error occurs during job release, the modal now surfaces a clear message instead of silently failing or leaving the form in a broken state.
Operations are now held behind their latest unfinished ancestor rather than only their direct predecessor, preventing work from being scheduled before all upstream steps are complete.
Reordering cards on the production board is now written atomically, eliminating the possibility of partial saves that could leave the board in an inconsistent state.
The ETA engine now fully accounts for competing work when projecting finish dates, preventing overly optimistic estimates caused by missing schedule data.
The board now loads work orders in bounded pages rather than attempting to fetch everything at once, keeping performance consistent as the number of active jobs grows.
The Gantt view now accurately shows why an operation's start time is constrained — for example, whether it's waiting on a predecessor or on machine availability — instead of displaying fabricated constraint indicators.