how-to · work Open this in the console

Run a script on a schedule.

A schedule is a time, a timezone, and the days. At that minute the hub starts the script on every machine it covers that is online.

A question the person has to answer, with no default, cannot be scheduled. There is nobody at the keyboard when it fires.

Write the script, then open the schedule

Company admins edit scripts. Open Scripts and press + script, or edit one already in the library. Run it on a schedule sits under the command. Leave it off and the script only runs when someone presses run. Run a saved script is that path.

Script editor with the schedule checkbox still off — New script. The schedule is off until you tick it.

Pick the time and the days

Tick run it on a schedule. Set the time, leave the days you want, and keep the timezone as the console's unless this company lives somewhere else. Every day is the default. A machine that is offline at that minute is skipped.

Schedule set to 02:30 with every day ticked — 02:30, every day, in the console timezone.

Save. The library shows when it runs

Press add to library (or save changes). The row gains a chip with the time. It runs itself from then on, on every machine this script covers that is online at that minute. Operators still see the chip. They do not edit the schedule.

Script library row with a schedule chip of 02:30 every day — Who is on the machine. The chip says 02:30, every day.

An offline machine is skipped, and the run history says so. It is not queued for later. Leaving the weekend off is Run a script on weekdays. Another clock is Run a script in another timezone. A run that is already going can be stopped from Scripts › runs — Stop a script that is still running.