How to Run an Integration Now and Pause All Schedules in EDGEBIC
User Solutions TeamTo run an integration immediately in EDGEBIC by User Solutions, select it in the left rail and click Run Now in the detail action bar, or click the play button on its card. To stop everything from firing on its own, tick Pause all schedules in the header strip. These are the two controls you reach for most, and they solve opposite problems: one forces work to happen now, the other stops work happening while you are busy.
Before You Start
| Prerequisite | Why |
|---|---|
| At least one integration is defined | These controls act on definitions, not on masks |
| You know whether you want a temporary or a persistent stop | Pause all schedules is session-only. A card's toggle is persistent |
| Access to the Integration tab | The tab is permission-controlled |
| You know a run changes data, not the plan | An integration never recalculates the schedule. That is a separate step |
Step 1: Run One Now
Select the integration in the left rail and click Run Now in the detail action bar, or use the play button on the card. Three things change at once: the card swaps to a progress bar, the chip starts counting rows as they are read, and the Live Log tab narrates the run while it is happening.
While a run is in progress, Run Now is replaced by Cancel Run in the same position. That is deliberate. The control that started the run is the control that stops it, so you are never hunting for a way out of a run you regret.
Step 2: Cancel a Run in Progress
Click Cancel Run. Rows already written stay written, which is worth saying out loud because people expect a cancel to roll back. It does not. A canceled run is recorded in Run History with its own status, so the record shows plainly that the run was stopped rather than that it failed on its own.
Step 3: Disable a Single Integration
Use the toggle switch on the right of its card. This stops both its schedule and its file watching, and the chip reads Disabled. The state belongs to the definition, so it survives a restart. Use this when one feed is wrong and the rest of the plant's syncs should carry on.
Step 4: Pause Everything for the Session
Tick Pause all schedules in the header strip. All scheduled runs and all file watching stop. Run Now still works, which is the useful part: you can keep pulling data deliberately while nothing fires behind your back.
This lasts for the current session only. Restarting clears it. That is a feature rather than an oversight, because the worst outcome for a temporary pause is that it quietly becomes permanent.
Step 5: Delete One, and Keep Its History
Click Delete in the action bar or the delete button on the card, and confirm. Its run history is kept for audit and stays visible under Run History when you tick All integrations (includes deleted).
How to Check It Worked
Open Run History and read the newest row. The Trigger column tells you which mechanism started it: Manual when you clicked Run Now, Schedule for the interval, FileWatch when the file changed, or Simulator. If you expected a manual run and see a scheduled one, or the reverse, you have learned something useful before it matters.
For a pause, the check is the absence of new rows plus the presence of a working Run Now. If Run Now is also dead, the problem is the host, not the pause. See checking whether anything is actually hosting your syncs.
Common Mistakes
Expecting the plan to move after a run. Runs change data, not the schedule. Jobs already scheduled carry their own frozen routing snapshot and are untouched. Run the scheduler yourself afterward.
Treating Pause all schedules as a persistent setting. It clears on restart. For a change window that spans a restart, disable the individual cards instead.
Clicking Run Now repeatedly when nothing appears to happen. A second trigger for a running integration is refused, not queued. The header tells you it is already running.
Deleting a noisy integration to silence it. Disabling it with the toggle keeps the definition and the option to bring it back. Deleting keeps only the history.
Next Steps
To set up the feeds these controls operate on, see how to create a watched-file integration and connecting EDGEBIC to your ERP database with a SQL source. To rehearse the whole mechanism against safe data first, see how to rehearse an integration with the EDGEBIC simulator. For the administrative view of a running estate, see administering scheduled ERP syncs.
Every task in this library is indexed on the EDGEBIC how-to hub. To see the whole feed and plan loop end to end, book a walkthrough of EDGEBIC.
Select the integration in the left rail and click Run Now in the detail action bar, or click the play button on the card itself. The card swaps to a progress bar, the chip counts rows as they are read, and the Live Log tab narrates the run while it happens. While a run is going, Run Now is replaced by Cancel Run, so the same button position gives you the way out. This is how you test a change or force a pull in EDGEBIC by User Solutions without waiting for the next interval.
Disabling one integration uses the toggle switch on its card and stops both its interval and its file watching, and its chip reads Disabled. It is a persistent state that belongs to that definition. Pause all schedules is a tick box in the header strip that stops every scheduled run and all file watching at once, and it lasts for the current session only, so restarting clears it. Under Pause all schedules, Run Now still works, which is the point: you can keep working by hand while nothing fires on its own.
Nothing collides. A second trigger for an integration that is already running is refused rather than queued, and the header says so. Two different integrations never run at the same time either, because the second waits its turn. A manual import you start from the Import screen and a scheduled run of the same mask also serialize, so whichever arrives second waits for the first to finish. Two writers can never fight over the same records.
Expert Q&A: Deep Dive
Q: We are cutting over this weekend and do not want anything importing while we work. What is the right control?
A: Pause all schedules is exactly the control for that, with one caveat you have to plan around: it lasts for the current session only. Restarting EDGEBIC clears it. For an afternoon of hands-on work that is ideal, because you cannot accidentally leave the plant's syncs off forever. For a change window that spans a restart, disable the individual integrations with their toggle switches instead. That state belongs to the definition and survives a restart, and each card reads Disabled so anyone looking at the screen can see what was done deliberately. Write down which ones you turned off, because the honest failure mode here is a sync that stays off for a month because nobody remembered it was a temporary measure.
Q: Someone deleted an integration. Have we lost the record of what it imported?
A: No. Run history outlives the integration itself. Open the Run History tab and tick All integrations (includes deleted) and the deleted definition's runs are still there, with their triggers, counts, durations and messages intact. That design decision is worth understanding, because it is what makes the history usable for audit. If deleting a definition erased its history, the question people actually ask, which is why a value changed on a particular Tuesday, would become unanswerable the moment someone tidied up the integration list. Keeping the runs means the answer is a row in a grid rather than a recollection.
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.
I Dragged an Operation and Nothing Happened: Fixing a Planner Drag in EDGEBIC
A drag that snaps back, stages nothing, or seems to be ignored on the EDGEBIC Planner board has a short list of causes. Read the status line, then work down this list.