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 PD Modules in the Blesta administration area.
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

Blesta manages PD Modules as two plugin cron tasks. One drains the installation/update queue; the other reaches scheduled module work. Open Settings → Company → Automation, or use that link from Jobs, and check the two PD Modules tasks and their recent outcomes.

The reviewed plugin registers a one-minute queue task and a five-minute general scheduler task. Those intervals depend on Blesta’s own cron actually running and the tasks being enabled. Use the installation’s configured schedule rather than assuming every task finishes within one minute.

PD Modules does not require a separate dedicated cron command on this platform. If work is stale, ask the Blesta administrator to check its native automation schedule and logs. Do not copy a dedicated-scheduler setup from a different platform or run every billing automation task merely to restart one module operation.

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 Blesta overview, follow the installation guide, or explore PD Modules.