To clarify more on the issue we are having (coworker here), here is an example of a row that failed to run:
<servername here>
Ping Reply
Reply from 172.29.0.102 time=0ms
Get Host Name
<servername here>
Schd Task – Action
Job queue (Patch REBOOT):: Start pinging
Get C: disk space
Get OS version / service pack level
Download and install updates + reboot always
Wait for host to go offline and come back online
Wait 3 minutes
Start stopped automatic services
Wait 1 minute
Stop pinging
Schd Task – Next Run Time
Sunday – 02/05/17 – 22:00
Schd Task – Recurrence
None
All Messages
Sun-22:00:37> Job Queue: Queued…
Sun-22:00:37> Scheduled Task: Initiating ‘Job queue (Patch REBOOT):: Start pinging
Get C: disk space
Get OS version / service pack level
Download and install updates + reboot always
Wait for host to go offline and come back online
Wait 3 minutes
Start stopped automatic services
Wait 1 minute
Stop pinging’ – Sunday – 02/05/17 – 22:00.
Sun-22:00:42> Job Queue: Queued…
Sun-22:00:42> Scheduled Task: Initiating ‘Job queue (Patch REBOOT):: Start pinging
Get C: disk space
Download and install updates + reboot always
Wait for host to go offline and come back online
Wait 3 minutes
Start stopped automatic services
Wait 1 minute
Stop pinging’ – Sunday – 01/29/17 – 22:00.
Fri-17:56:05> Get host name: <servername here>
Fri-17:56:05> Get host name: Attempting to retrieve host name…
We have noticed that when that happens, it usually happens in all* rows of a bps file. The same scheduled job is ran in many other bps files with no issue.
*With the exception of a row that has a scheduled notification email sent much later.