Scheduled bundles run in a serial manner. All scheduled bundle actions are added to a run queue on the agent side. The bundle actions are added to the queue according to the bundle schedule. However, the bundle actions are then executed in the order in which they were added to the queue. This design can result in bundles seeming to run off the schedule, if prior scheduled bundles have not finished their action sets by the time the next bundle schedule is reached.
Consider the following scenario:
Bundle A is scheduled to launch at 10:00 AM and Bundle B is scheduled to launch at 10:30 AM.
The launch action set for Bundle A takes 1 hour to complete.
Bundle B launches at 10:30 AM according to the schedule.
However, the launch actions for Bundle B will start only at 11:00 AM after Bundle A’s launch actions have been completed.
Now consider that Bundle B performs a reboot that should only have been performed at the scheduled time. In this case, to prevent the reboot from running at unwanted times, you would have to set action level system requirements. For example, an action level system requirement could be either to perform the reboot if a user is not logged into the workstation or to show a prompt allowing the user to cancel the reboot.
NOTE:The optiondoes not apply in the above scenario. This option is only meant for scenarios where the workstation is not running when the scheduled time occurs.