Schedule a governed script rule
Create a time-zone-aware schedule, scope it to devices, add an eligible script, and review projected and actual runs.
Before you start
- Create and review the script first.
- Know the intended device scope, local time zone, and acceptable execution window.
Screenshots show the Rapport interface with example data. Use your organization’s devices and values. Select an image to view it at full size.
Start a scheduled rule
Open Rules → New rule, choose Scheduled, and enter a clear name and key. New rules begin in Shadow so their behavior can be reviewed before activation.
What you should see: The rule editor is in Scheduled mode with detection-only fields cleared.
Choose the schedule and time zone
Select Hourly, Daily, Weekly, Monthly, or Custom. For calendar presets, set the displayed wall-clock fields and choose the named time zone. Read the generated description and next occurrences before continuing.
| Field or control | What to do |
|---|---|
| Time zone | Stored separately from the five-field schedule so daylight-saving behavior follows the selected zone. |
| Custom | Use a valid five-field cron expression supported by the editor. |
Set the device scope
Choose platforms, tags, organizational units, and/or explicit devices. Review the matched count and projected daily dispatches. Narrow the scope when the projection is larger than intended.
Add the script step
Choose an enabled machine-context script and a compatible platform, then supply its required parameters. Scheduled rules run scripts only; ticket steps belong to detection-triggered rules.
What you should see: The rule has at least one valid, reviewable script step.
Add operational limits
Set cooldown, maximum runs per hour, priority, and an optional maintenance window. Schedule rules do not use alert verification or a success floor. Confirm the generated sentence before saving.
Save, observe, and activate deliberately
Save the rule in Shadow. Open the rule and Activity to review would-run or actual records. Activate only after the scope and timing are correct; pause the rule when dependencies or results need attention.
What you should see: The schedule is represented by a revisioned rule with visible scope and history.
If something doesn’t work
The next times are not what I expected.
Check the selected time zone, preset fields, and the generated next occurrences before saving.
Projected dispatches are too high.
Narrow the scope, reduce schedule frequency, or lower the hourly cap.
The scheduled rule did not run.
Check its state, current time zone, maintenance window, script availability, device match, and Activity records.