When Joomla Lazy Scheduler Is Appropriate for QCUL

Joomla Lazy Scheduler can be sufficient for QCUL maintenance on sites with dependable frontend traffic, but it is traffic-dependent and therefore less predictable than server cron.

When Lazy Scheduler is reasonable

• The site receives regular real traffic throughout the day.
• A delayed cleanup/safety check by some minutes is acceptable.
• You monitor Scheduled Task execution and know the scheduler is actually advancing.

When to prefer server cron

• Low-traffic/private sites.
• You need cleanup/safety checks close to their configured cadence.
• You already operate infrastructure cron for other Joomla tasks.

QCUL does not replace the trigger

QCUL provisions/repairs its task rows but does not itself create the hosting cron. Check Last Execution/Next Execution in Joomla Scheduled Tasks to confirm the chosen trigger mechanism is working.

Scheduled-task verification

After changing or repairing When Joomla Lazy Scheduler Is Appropriate for QCUL, verify the canonical task row in System → Scheduled Tasks: enabled/disabled state, Last Execution, Next Execution, and Last Exit Code. Registration alone does not prove the maintenance routine runs; Joomla Scheduler still needs Lazy Scheduler or server cron to trigger due work.

Community Discussion

Want to compare update-testing workflows, share practical tips, or discuss how you use this QCUL feature? Visit the QC Update Laboratory Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.