How to Cancel a Scheduling Run in Progress in EDGEBIC

To cancel a scheduling run that is already in progress, click Cancel on the Scheduling Manufacturing Orders progress overlay; the run stops, nothing partial is kept, and the plan you had before you pressed the button is still there. In EDGEBIC by User Solutions a run is computed and then written, never committed job by job, so an abandoned run leaves no wreckage to clean up.

This post covers only the mid-flight stop. For the run itself, start with how to run the production scheduler, and the full task library is at the EDGEBIC how-to hub.

Before You Start

• A run is actually in progress, which means the progress overlay is on screen and the order grid is locked.
• You understand the difference between canceling a run and clearing a schedule. Cancel abandons a calculation. Clearing a job's schedule deliberately removes an existing plan.
• You know what the run was going to touch. If you never read the Confirm Scheduling dialog, canceling is the right instinct, because you were about to move an unknown number of jobs.

The Steps

1. Find the overlay. During a run, the Drive Schedule tab is covered by the Scheduling Manufacturing Orders overlay. It carries a progress bar, a status message naming the current phase, an elapsed-time readout, and a Cancel button.
2. Read the status message once before you act. The message moves through phases: initializing the scheduler, loading configuration data, then scheduling the orders. A long pause inside one phase on a big run is normal, not a hang.
3. Click Cancel. There is no second confirmation, because there is nothing to confirm away: no plan has been written yet.
4. Watch the overlay close and the grid unlock. The status line reports that the operation was canceled.
5. Check one job you expected to move. Its dates and its Scheduled or Unscheduled badge should read exactly as they did before the run.
6. Fix whatever prompted the cancel, then run again. Usually that means re-ticking the correct Select checkboxes, or correcting a priority or due date that the lock had been stopping you from editing.

What Changes When You Cancel

The reason this is boring rather than dangerous is the write model. A run holds its result until it is complete, then saves. There is no per-job commit that could leave job seven planned and job eight stranded.

How to Check It Worked

Pick the job whose row you were watching before the run and compare three things against your memory or a screenshot: the Status badge, the Schedule Details line, and Days Late. All three should be identical to their pre-run values. A job that was Unscheduled should still read Not scheduled yet, not a half-filled set of dates.

Then confirm the grid is live again by typing into a Priority cell. If the cell accepts the keystroke, the lock has lifted and the run is genuinely over. Finally, open Job View on one job and confirm the hours header still shows the same Total Hours and Actual Hours it did before.

Common Mistakes

Assuming a canceled run left the plan half-done. It cannot. This is the single most common worry and it is unfounded. There is no partial-save state, so there is nothing to hunt for and nothing to undo.

Canceling the wrong Cancel. If you are running backward jobs with the review popup enabled, a separate dialog can appear at the end of the run listing jobs that cannot make their due dates. Its Cancel button also discards everything, but that is a decision about a completed calculation rather than an abandoned one. The distinction is explained in scheduling a job backward from its due date.

Canceling repeatedly instead of narrowing the scope. If runs keep taking longer than you are willing to wait, the fix is scope, not patience. Tick the specific jobs you need re-planned instead of accepting the Schedule All Orders offer, and see how to reschedule only the jobs that changed.

Trying to edit an order through the lock. The grid is disabled on purpose so an edit cannot land inside a calculation that already read the old value. Cancel first, edit, then run.

Treating the cancel as a way to preview. It is not a dry run. The overlay shows progress, not results, so nothing is revealed by letting it get most of the way there. The real preview is the Confirm Scheduling dialog, covered in how to see which jobs a run will touch before you commit.

Next Steps

Once you have canceled, the useful question is what you meant to run instead. If a single job needs a fresh plan, scheduling one job is faster and quieter than a plant-wide pass. If the run was going to take longer than you expected because it included everything, tighten the selection and re-read the confirm dialog. And if the plan that survived your cancel is itself wrong, the diagnostic order is capacity first, calendars second, as laid out in how to see why a job is late.

The takeaway

Canceling a scheduling run in EDGEBIC is a genuinely safe action, and knowing that changes how you plan. You can press Schedule and Re-Schedule to see how long a run takes, stop it, tighten the scope, and try again, without ever putting a committed plan at risk. That confidence comes from one design decision: the engine writes a complete result or it writes nothing. See where finite-capacity scheduling fits on the EDGEBIC product page, and if you are arriving from the earlier generation of User Solutions planning tools, the move from RMDB to EDGEBIC shows what carries over. Next, read how to run the production scheduler end to end, then how to check what a scheduling run changed so the run after this one needs no guessing at all.