A user asked about recommended timeout when running a script – ControlUp suggested that for simple scripts, 60-120 seconds should suffice, but for more complex scripts, longer timeouts can be set. Depending on the complexity of the Script, averages can be gathered to configure the timeout. The Support page for Script Configuration Options is https://support.controlup.com/docs/scripting-guide#script-configuration-options.
Read the entire ‘Timeout Guidelines for Running Scripts with ControlUp’ thread below:
Good day
Happy Friday , wow i have not posted in some time 😄
Quick Question , when running a script , is there a recommended TimeOut ?
or can i set it to 10 min (1200s) or more , the script that im busy with now can take some time to complete and i down want to kill it if it still busy
Hi @member I think it can be circumstantial, for simple scripts 60-120 should suffice but for more complex scripts, it could take much longer than that. You can try setting it to 0, see how long it takes, and then adjust accordingly. Reference: https://support.controlup.com/docs/scripting-guide#script-configuration-options

Hello @member thank you for the reply , the script does one big thing on the device and it can take some time for it to finish but when it does finish I need to see the response from it does asking this
Unfortunately I can say how long it will take , each device will differ
maybe you can gather some averages and then configure the timeout with that. If the script is finished before the timeout, there shouldn’t be any issues with that so even if you set it longer than what it will go past, it should be fine.
Thanks
, awesome a awesome weekend
Continue reading and comment on the thread ‘Timeout Guidelines for Running Scripts with ControlUp’. Not a member? Join Here!
Categories: All Archives, ControlUp for Desktops, ControlUp Scripts & Triggers
