How QCTNH Enables and Prepares Joomla WebCron

QCTNH prepares native Joomla WebCron automatically: it enables Schedule Runner, enables WebCron in com_scheduler, and creates a native key when necessary.

Preparation sequence

  1. Find System - Schedule Runner; enable it if installed but disabled.
  2. Find the Joomla Scheduled Tasks component (com_scheduler).
  3. Read its component parameters and look for webcron.key.
  4. If the key is empty, generate a 20-character key using Joomla’s password helper.
  5. Set webcron.enabled=1.
  6. Remove legacy/custom webcron.base_link and webcron.reset_key parameters so Joomla core remains authoritative.
  7. Save the Scheduler component parameters.

What QCTNH deliberately leaves alone

It does not change Joomla’s Lazy Scheduler settings. WebCron readiness and Lazy Scheduler are separate choices.

Execution boundary

For How QCTNH Enables and Prepares Joomla WebCron, remember that one WebCron request is an execution opportunity, not a command to run a named task. QCTNH never sends a task ID to force selection. Joomla receives its normal System - Schedule Runner request, applies its queue/lock/recurrence rules, and returns the result of the work it chose.

This design is why QCTNH can work with Scheduled Tasks from many extensions without knowing their business logic. It also explains why a task-specific error belongs first to the owning extension even when QCTNH successfully delivered the WebCron request.

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.