Schedule Not Running

This guide will provide troubleshooting steps in the event that your PDQ Deploy Schedules fail to run on one or more targets. 

Schedule is Not Running for Specific Targets

If a Schedule is running as expected but not initiating the deployment for some targets:

Check Schedule Triggers

Verify that the Schedule has appropriate triggers that suit the Schedule's purpose. 

A Schedule with only a Heartbeat trigger configured will only deploy to targets as PDQ Inventory detects them going from an offline state to an online state, but will not deploy to targets that are always powered on and connected to the network.

Using a Daily Trigger along with a Heartbeat Trigger will run the Schedule every day at the scheduled time, and the Heartbeat Trigger will catch the targets that were offline when the Daily Trigger ran. If the Daily Trigger is consistently failing for more targets than it reached, try adjusting the trigger time to run the Schedule when more targets are expected to be online.

Check Schedule Options

Check the following settings in the Options tab:

Stop deploying to targets once they succeed - With this setting enabled, the Schedule will no longer run against targets that have successfully received the deployment. This applies to the lifetime of the schedule, not just individual triggered deployments. This setting should remain checked for Auto Download Packages, because the Target History for any Schedules they are attached to will clear upon the Auto Download Package Updating. 

• Uncheck this option if the deployment needs to be ran more than once per-target.
• Delete the affected target from the Schedule's Target History tab to have the Schedule run against that target while preserving the setting.
• Note: This setting is the most common reason why a schedule will fail to run on a target more than once.

Stop deploying to targets if they fail _ time(s) - If this setting is enabled, the Schedule will no longer run against targets that have failed more than the configured amount of times. 

• De-select this option to have the Schedule continue running against a target, regardless of how many times it fails.
• Delete the affected target from the Target History tab of the Schedule, to allow the Schedule to run against that target again while preserving the setting.

Stop deploying to remaining queued targets after _ minutes - Enabling this setting will cause PDQ Deploy to cancel the deployment for any queued targets after a set amount of time. Currently running targets will finish the deployment.

• Make sure the time configured here (if enabled) is enough time for the deployment to run on each of your target computers.
• If this setting is configured, check the Deployment Timeout (Options > Preferences > Deployments) and the Concurrent Targets / Concurrent Per Deployment settings (Options > Preferences > Performance) to make sure there aren't any unintentional conflicting settings that would prevent the Schedule from completing.

Schedule Triggers Not Working

If a Schedule Trigger is not initiating a Schedule's deployments for all expected targets:

1. Delete and re-create the Schedule Trigger.
   • If the Schedule Triggers still fail to activate, continue to Step 2.
2. Delete the Schedule Trigger, Duplicate the Schedule (right click > Duplicate or Alt+Insert with the Schedule highlighted), and add the desired Triggers to the duplicated Schedule.
   • Be sure to disable the original Schedule before the duplicated Schedule's Trigger(s) are set to run.
   • If the Schedule Triggers still fail to activate, continue to Step 3.
3. Close the PDQ Inventory Console and restart the PDQ Inventory service.
   • If the Schedule Triggers still fail to activate, continue to Step 4
4. Reboot the PDQ server.