Source
r/labtech•
teamits

Script timeouts for offline computers is now only 2 hours

I've been told by support that CW has quietly and gradually been shortening the timeout for when scripts run on an offline computer give up and "fail." The tech said they are down to 2 hours now. There is no way to change this timeout.

For us this is a problem because when we set our system up we installed Windows Updates on Monday night, and Tuesday night we ran a bunch of scripts for PCs with Flash, Java, etc. In times past I recall scripts that schedule on Tuesday night were still waiting on Thursday or maybe even Friday. Also, I have frequently left a restart, fixit, or other script running on an offline PC that went to standby, so it runs when it comes online.

It seems we'll have to rethink all our overnight script scheduling, and either run during the day or run every few hours for a few days.

Enhancement request regarding this:

https://product.connectwise.com/communities/5/topics/12374-modify-script-timeout

I guess the workaround for overnight scripts is to schedule the script at 2 am and then run every 2 hours for 6 days? Then add a check to the top of the script to exit if the program was updated already.

Posted Oct 23, 2018, 7:28 PM UTC

24
gibsurfer84•

That’s shitty. Typical labtech.

2
chilids•

Good to know. I counted on these scripts sitting in the queue as well.

1
Tim_Theory•

Do I understand correctly that this is for scripts scheduled without the "Skip if offline" option ticked?

"Skip if offline" not running a script on an offline agent, with the alternative also not running the script on an offline agent, seems... silly.

1
teamitsOP•

Correct, if "skip" is checked it will not run on offline agents. If unchecked it will wait 2 hours.

2
teamitsOP•

It seems that in patch 10 (?) this was quietly reverted since I discovered this month (and support confirmed via their testing) that scripts stay scheduled for at least 48 hours.

1