- Home
- Blog
- EDGEBIC How-To
- How to Put a Job On Hold in EDGEBIC
To put a job on hold in EDGEBIC, keep it out of your scheduling runs and clear its schedule so the capacity it was holding goes back to the plant. There is no button that pauses a job while leaving it on the plan, because a paused job that keeps its work center reservations is worse than useless: it blocks machine hours nobody is going to use. EDGEBIC by User Solutions handles a hold as two plain acts, releasing the plan and controlling the run scope.
This is a task post. For the broader run mechanics it depends on, read how to run the scheduler in EDGEBIC, and browse the rest at the EDGEBIC how-to hub.
Before You Start
- The job exists on the Drive Schedule grid, whether it is scheduled or not.
- You know whether operators have logged work on it. Check the Actuals Logged? column.
- You understand the scope rule: ticked rows define what a run touches, and unticked jobs keep their plans.
The Steps
- Open the Schedule area and select the Drive Schedule tab.
- Tick the Select checkbox on the held job only. Untick everything else. This scope matters for the next step.
- Click Clear Schedule on the filter bar.
- Read the scoped confirmation. With rows ticked, only those jobs' schedules are cleared. With nothing ticked, the prompt asks whether to clear all schedules, which is not what you want here.
- Confirm. The job returns to the Unscheduled badge, its Schedule Details goes back to "Not scheduled yet", and its Completed? flag is reset if it had been ticked.
- Leave it unticked from now on. Every future run you make with specific rows ticked will pass it by.
If you want the hold visible to colleagues rather than implied, note it in the Assigned To field or record the reason in the job's audit history so the next planner does not schedule it back in by accident.
What Changes When You Save
| Surface | Effect of clearing a job's schedule |
|---|---|
| The order | Untouched. Product, quantity, due date, priority and direction all survive. |
| The plan | The job's operations are removed. Its bars disappear from the Gantt. |
| Work center capacity | The hours the job was holding are released and available to other jobs on the next run. |
| Recorded work | Actual start and end dates that operators logged remain on the job. |
| Completed? | Reset for cleared jobs. |
| Other jobs | Untouched. Only the ticked rows are cleared. |
The released capacity is the reason to clear rather than simply avoiding the job in your runs. Leave the plan in place and the machine hours stay reserved: the plan says the mill is busy Tuesday, so nothing else gets planned there, and Tuesday is spent on nothing at all.
How to Check It Worked
Look for three things on the row: the Unscheduled badge in the Status column, "Not scheduled yet" under Schedule Details, and empty Item Start and Job End columns. Then open the Job View tab or the Gantt and confirm the job's bars are gone.
To confirm the capacity actually came back, run the scheduler for the jobs that were queued behind it on the constrained work center. If they now start earlier, the hold released real hours.
Common Mistakes
Deleting the order instead of clearing its schedule. Deleting is permanent and takes the job's production schedules with it, and the confirmation says so. A hold is temporary by definition. Always clear.
Clearing with nothing ticked. With no rows selected, Clear Schedule asks whether to clear all schedules and wipes the entire plan if you say yes. Tick the one row first and read the prompt before confirming.
Answering yes to Schedule All Orders afterwards. That prompt only appears when no rows are ticked, and it sweeps every order into the run including the one you held. Tick specific rows before you press the schedule button, or answer no.
Assuming a hold protects the recorded work from a later reschedule. It does not need to. Completed and in-progress operations are never moved by a reschedule in the first place, and clearing a schedule does not delete the actual dates. When the job comes back, the engine resumes from where the floor got to.
Bringing the Job Back
Tick the row, run the scheduler, and confirm the job counts in the dialog. The job is planned against the plant as it stands on the day you release it, not as it stood when you paused it, which is the right answer: two weeks of other work has been booked in the meantime. Check Days Late afterwards, because a paused job usually comes back with less runway than it left with.
What to Do Next
If the pause turns out to be permanent, how to cancel a manufacturing order covers the difference between clearing, cancelling and deleting. If the released job comes back late, work the checklist in how to see why a job is late. For the wider argument on keeping plans stable rather than constantly reshuffled, how EDGEBIC reduces schedule churn is worth ten minutes, and the EDGEBIC product page covers the platform.
Expert Q&A: Deep Dive
Q: A customer paused an order for two weeks. What is the cleanest way to park it?
A: Clear that job's schedule and leave it out of your runs. Tick only that row, click Clear Schedule, and confirm the scoped prompt. The order stays in the grid as Unscheduled with its quantity, due date and priority intact, and every hour it was holding on your work centers is immediately available to other jobs on the next run. That last part is the whole point: a paused job that keeps its reservations quietly starves the jobs that could have used the machine. When the customer releases it, tick the row, run the scheduler, and it gets a fresh plan against the plant as it stands then.
Q: The job is half built. Can I still hold it?
A: Yes, and the recorded work is safe. Clearing a schedule removes the plan, not the history: the actual start and end dates operators logged remain on the job. When you bring the job back and re-run it, the engine resumes from where the floor actually got to and only re-plans the remaining steps. Before you clear, note the job's Actual Hours and Percent Complete from the Job View summary panel so you have a reference point, and check the audit trail afterwards to confirm the recorded work is intact.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
