How Joomla Lazy Scheduler Works

Joomla Lazy Scheduler uses ordinary site requests as opportunities to run due Scheduled Tasks, which is convenient but inherently tied to traffic.

How Lazy Scheduler behaves

When enabled, Lazy Scheduler can use frontend activity to give Joomla’s scheduler work opportunities without server cron. A busy site may therefore keep tasks moving naturally; a low-traffic site can miss the intended timing simply because no suitable request arrives.

QCTNH coexistence

QCTNH 2.0.3 explicitly leaves lazy_scheduler.* settings unchanged. You can keep Lazy Scheduler enabled. The two mechanisms complement each other: traffic can trigger work while QCTNH provides native-WebCron wake-ups during quiet periods.

Do not interpret two trigger sources as two task runners

Both paths ultimately hand control to Joomla Scheduler. Joomla’s task state and locking still govern execution. QCTNH is not a second scheduler implementation.

Timing consequence

The scheduler rule described in How Joomla Lazy Scheduler Works also affects when QuantaCade should wake the site. QCTNH reports aggregate next_due, whether that value is known, and a due count. When an exact future time is known, the central service can sleep toward that point instead of generating fixed high-frequency traffic.

If timing is unknown, QCTNH falls back to the configured Maximum Scheduler Delay and safety rechecks. Therefore a timing problem should be diagnosed from the scheduler snapshot first, not by assuming the service is simply a cron request every N minutes.

Community Discussion

Want to compare scheduler workflows, share practical tips, or discuss how you use this QCTNH feature? Visit the QC Task Nudge & Health Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.