// docs

Job Planner

Schedule any script, runbook, installer, or S.E.N.T.R.I prompt to run once or on a repeating interval — and let the service run it while no one is logged in.

Creating a schedule

In the Job Planner, pick what to run (a script, runbook, installer, or a S.E.N.T.R.I prompt), the target host or group, a date and time, and a repeat interval. Add parameters if the run needs them, then enable it. Schedules can be disabled and re-enabled without deleting them.

Repeat intervals

Interval	Runs
One time	Once, at the specified date and time.
Every 5m – 12h	Repeating: 5m, 15m, 30m, 1h, 2h, 3h, 6h, or 12h.
Daily (24h)	Every day at the set time.
Weekly (7 days)	Every seven days.
Monthly (28 days)	Every 28 days.

How schedules run

Enabled schedules are registered with Windows Task Scheduler and executed by the ServerEngine automation service. That means they run headlessly — on time, whether or not the console (or any user) is signed in. Scripts, runbooks, installers, and S.E.N.T.R.I prompts all run the same way. Results and output land in the Logs just like interactive jobs.

Scheduled prompts

A scheduled prompt puts the agent on the clock: give S.E.N.T.R.I a goal in plain language, point it at a host or group, and the service runs it on your interval. The agent plans, calls the skills you have enabled, and writes the whole conversation and every action to the Logs — so an unattended run is as traceable as a script.

Approvals are interactive-only

An approval prompt has no one to answer it in an unattended run, so approval-required skills are skipped on a schedule. Your guardrails on a scheduled prompt are the scope it runs in and the set of skills you left enabled. Scope tightly before you put a prompt on a repeating interval.

Trigger schedules from the API

You can also create and run schedules through the REST API — useful for provisioning recurring jobs from infrastructure-as-code or another system.