How to Enable the Joomla Lazy Scheduler

Enable Joomla's Lazy Scheduler when you want normal frontend traffic to provide execution opportunities for Scheduled Tasks. It is easy to operate because it does not require shell access or an outside cron service, but it is traffic-dependent: a task can run only after it is due and a qualifying site request gives Joomla an opportunity to check scheduled work.

Confirm Lazy Scheduler is appropriate for the workload

Lazy Scheduler is a good fit for maintenance and other work that can tolerate approximate timing on a site with regular frontend traffic. It is a weaker fit for low-traffic sites or jobs that must start predictably at a particular time.

Before changing the global trigger, identify which tasks depend on automatic execution. If strict timing matters, consider a server cron invoking Joomla's CLI scheduler or another deliberately scheduled trigger instead.

Enable Lazy Scheduler in Scheduled Tasks options

  1. Sign in to Joomla Administrator.
  2. Go to System → Manage → Scheduled Tasks.
  3. Select Options from the toolbar.
  4. Locate the Lazy Scheduler settings.
  5. Set Lazy Scheduler to Enabled.
  6. Review the Request Interval; Joomla documentation lists 300 seconds as the default.
  7. Save the options.

The request interval limits how often visitor traffic can create scheduler checks. It is not an exact execution interval for every task.

Check the individual tasks

Enabling the global trigger does not enable task records or change their execution rules. Return to the Scheduled Tasks list and confirm each task you expect to run is enabled, correctly configured, and scheduled at a sensible frequency.

Use Test Task for a safe task before relying on automatic execution. A successful manual test proves the task logic can run and keeps task-specific failures separate from trigger problems.

Verify a visitor-triggered execution

  1. Allow the tested task to become due.
  2. Allow the configured request interval to pass.
  3. Generate normal frontend traffic to the site.
  4. Check the task's Last Run information or Execution History where available.
  5. Verify the real-world result the task was intended to produce.

Do not treat a page view alone as proof that the task executed. Verify the task record and its actual outcome.

Troubleshoot when nothing runs

If manual execution succeeds but Lazy Scheduler does not produce an automatic run, confirm the task is enabled and actually due, the Lazy Scheduler option remained enabled after saving, and frontend requests are reaching Joomla rather than being fully served by an upstream cache. Review Joomla and PHP logs for execution errors.

If the site simply does not receive enough qualifying traffic, the configuration may be correct but operationally unsuitable. In that case, use a predictable external trigger rather than shortening the request interval repeatedly.


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