A user asked about the behavior of ControlUp when running long scripts. It was clarified that if the same script is rerun before the first one finishes, a separate process will be started and the scripts will run one after another. It was also mentioned that this process will soon be automated and trigger only runs daily if needed. This was done to prevent running the scripts manually too aggressively.
Read the entire ‘Running long scripts in ControlUp and its behavior’ thread below:
Hi again! Just a general question here. I have a script that can take a while to run depending. What happens when someone runs a long running script, then rerun the same script before the first script finishes? Does CU do some orchestration magic so they just run one after another? Do they run on top of each other?
a separate process will be started that runs it so it doesn’t take into account existing scripts
Is it an automated action?
Soon to be automated, and I have the trigger written to only run daily if needed at all. I found a colleague had been running the script manually against batches of machines, just a little too aggressively for my comfort. No real harm, just wanted to confirm.
Continue reading and comment on the thread ‘Running long scripts in ControlUp and its behavior’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI, ControlUp Scripts & Triggers