Use the Jobs page to distinguish a queued installation or update from a scheduled module task. Check the current operation before repeating it; requesting the same action again does not establish what happened to the first attempt.

Find the affected work

1. Open Addons → PD Modules.
2. Open Jobs.
3. Check Active now for queued or running installs and updates.
4. Review Scheduled jobs for the module and task you are investigating. Expand its group, or use Filter jobs or modules… when the filter is shown.
5. Note Runs, Last run, Outcome and Next due, including any message beneath the outcome.
6. Review Installs & updates for the result of a completed installation or update, and Recent runs for scheduled-job history when available.

The install/update queue and a module’s recurring task are different kinds of work. A scheduled task being healthy does not prove an installation completed, and a completed installation does not prove every provider operation works.

Check whether the task is enabled and due

A task marked Off or disabled is not necessarily broken. Ask the administrator who manages it whether that was intentional. Check the module’s own settings as well: a task can run successfully and report that its optional feature is disabled or that there is nothing to do.

Compare the task’s interval and Next due with the current time. A short interval does not make a task run more often than the scheduler that reaches it. Read the outcome, not just a health summary or the fact that a timestamp changed.

Check the platform schedule

By default PD Modules uses the WHMCS cron. The Jobs page also supports a dedicated schedule. Review Running jobs now and any warning such as No cron tick received yet, Your cron may not be running or Dedicated cron not detected. The selected mode is a preference; the detected runner and recent task outcomes are the evidence that work is reaching the panel.

Ask the administrator or hosting provider to check the existing WHMCS cron and, if used, the dedicated schedule. Confirm recent execution reaches PD Modules itself. A healthy platform cron alone does not prove a particular module task ran successfully. Do not add a duplicate schedule or replace a working one merely because one task is not yet due.

The panel can show the installation-specific command for an optional dedicated cron. This guide does not reproduce server paths or commands: have the administrator review the panel’s own instructions and verify the detected runner afterwards.

Investigate a failure without duplicating work

Read the exact result and error code before changing anything. The Start now, Run now and Run all due now buttons perform work; they are not read-only diagnostics. Use a manual run only when you understand that task’s effects and the previous operation’s state.

If an action can create a service, send a notification or change a provider resource, reconcile its actual outcome before another attempt. A timeout or stale progress indicator is not proof that nothing happened.

Read the PD Modules WHMCS overview, follow the installation guide, or explore PD Modules.