Scheduled Windows FAQ

The following answers address common questions about how scheduled windowsClosed Defined time periods controlling when Automox runs policies. interact with policiesClosed Represents a set of logic statements that define the desired target state of a device, the allowed remediation schedule, and configuration parameters around how that remediation should take place., devicesClosed A subset of Assets, a general term denoting anything that runs the Automox Agent and is registered with the system., and manual actions in Automox. You can currently create exclusion windows, and additional window types might be added in the future.

ClosedWhat happens if a policy is scheduled during an exclusion window?

If a policy’s scheduled run time falls within an active exclusion window, Automox prevents it from executing. The policy run is marked as Blocked in the Policy Results Report and logged as an Activity in the Activity Log, both displaying the reason identified as “scheduled within an exclusion window.”

ClosedWhat happens if a policy starts before an exclusion window begins?

If a policy or worklet has already started when an exclusion window begins, Automox allows the current task to complete but does not start new tasks until the window ends. The results show as Partial Success for the incomplete portions.

ClosedCan I manually run a policy during an exclusion window?

Yes. You can manually run a policy, worklet, or required software task during an active exclusion window if you have execution permissions. Automox displays a confirmation dialog before continuing. If you proceed, the action is logged in both the Activity Log and the Policy Results Report as a manual bypass of the exclusion window. Policy runs via Run Now / Fix Now cannot be run as a manual bypass of the exclusion window.

ClosedDo exclusion windows apply to all policy types?

Exclusion windows apply to all policy types: Patch All, Severity, Patch Only, Manual Approval, Patch All Except, Advanced, as well as Worklets and Required Software policies.

ClosedAre tasks queued to start after an exclusion window ends?

No. Tasks or policies scheduled during an exclusion window do not automatically run when the window ends. They wait for their next scheduled cycle.

ClosedWhat happens if I edit an exclusion window while it is in progress?

If you change an exclusion window that is currently in progress, your changes take effect immediately. Modifying an active window can cause scheduled policy runs to resume once the change takes effect.

ClosedWhat happens if I delete an exclusion window that is in progress?

Deleting an active exclusion window immediately removes its restrictions. Policies or other scheduled work that fall within that time period can run once the deletion takes effect.

ClosedWhat time zone do exclusion windows use?

All exclusion window times are currently displayed and scheduled in UTC. Recurring and one-time schedules both use this standard.

ClosedWhat happens when an exclusion window activates while a policy is executing?

  • If the current package being installed is a third-party package, the installation completes and no further packages are installed.
  • If first-party updates are downloading but have not yet started installing, no first-party updates install.
  • If first-party packages have started installing, all first-party updates complete but no further packages are updated.
  • If a patch requires a restart, the device does not restart and remains in a Needs Restart state until the command is triggered again.

Related Topics