Ability to Disable an Integration (2 replies)
I have an integration that is run via command line and, at the moment, I have too many running causing the server to run slowly. I need a way to stop more from spawning but I can barely open a command prompt to close down the utility. If I had a way to disable an integration that would allow us to prevent any thing from running new instances (IMan scheduler, windows scheduler, etc).
Another example: I had to shut down all Integrations at a client except for one while a new piece of functionality was implemented. I wanted to run the one Integration manually. I had to delete the schedules of all of the other Integrations since shutting down the Scheduler service prevents me from running it through the interface. If I could disable all of the other Integrations I wouldn't have to delete/recreate the schedule and I could keep the scheduler service running.
Good idea. I often need to pause scheduled integrations and I don't want to have to create them all from scratch again afterwards, as they tend to have varying run times and frequencies. For a while I was doing it by changing the start date to some time it the future, but I found that this creates thousands of errors in the IMan Audit log so is not a viable approach.