How to Fix Joomla Scheduled Tasks Not Running

When Joomla Scheduled Tasks are not running, separate the problem into two layers: can the task itself execute, and is Joomla receiving a working automatic scheduler trigger? Testing those layers in order prevents unnecessary changes to cron, Web Cron, Lazy Scheduler, or task configuration.

Confirm the task is enabled and actually due

  1. Open System → Manage → Scheduled Tasks.
  2. Find the affected task and confirm it is enabled.
  3. Review its execution rule and next execution information.
  4. Confirm it is configured for automatic execution rather than intentionally manual-only operation.

A disabled task or a task whose next execution is still in the future is not a scheduler failure.

Test the task manually

Use Joomla's task test for a task that is safe to rerun. If it fails manually, troubleshoot the task plugin, its parameters, permissions, files, database state, credentials, or external dependencies before changing the automatic trigger.

If it succeeds manually, you have strong evidence that the remaining problem is scheduling or an execution-environment difference.

Verify the site's automatic trigger

Identify the trigger the site is intended to use. Lazy Scheduler depends on frontend traffic. Web Cron depends on a trusted external request to Joomla's generated protected URL. Server cron depends on the hosting scheduler invoking Joomla's CLI command successfully.

For server cron, run the exact PHP executable and absolute Joomla CLI path manually, then inspect the hosting cron history or captured output. For Web Cron, inspect the external service's HTTP result. For Lazy Scheduler, confirm it is enabled and the site receives normal frontend requests.

Use execution history and logs to locate the failure

Where available, review Scheduled Tasks Execution History for the last run time, duration, and exit result. A recent failed execution means Joomla reached the task; no recent execution for an overdue task points more strongly toward the trigger or due-state evaluation.

Correlate the same timestamp with Joomla logs, PHP errors, web-server logs, extension logs, and cron output.

Check timeouts and environment differences

Review the Scheduled Tasks global Task Timeout and relevant hosting limits. Do not increase limits blindly; determine whether the task is slow because of database work, network calls, large files, or another dependency.

A CLI cron job can also use a different PHP version, php.ini, user account, permissions, PATH, or working directory than a browser request. Compare those environments if manual web execution works but cron does not.

Prove the fix with an automatic run

  1. Make the smallest justified correction.
  2. Retest the task manually if appropriate.
  3. Allow it to become due again.
  4. Wait for the normal automatic trigger.
  5. Confirm a new successful execution record.
  6. Verify the task's real-world result.

Do not stop at a successful manual test. The final automatic run is what proves the scheduler path is fixed.


Need More Help with Joomla?

Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.

Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.

QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.

Open a Support Ticket