How Joomla Scheduled Tasks Are Triggered

Joomla Scheduled Tasks do not execute merely because their scheduled time arrives; Joomla must receive a scheduler trigger through Lazy Scheduler, WebCron, CLI, or another supported mechanism.

The execution chain

  1. A task plugin registers a routine with Joomla Scheduler.
  2. Joomla stores an enabled task row with its schedule and next_execution.
  3. When a trigger reaches the Scheduler, Joomla evaluates eligible task routines and locking.
  4. Joomla runs the next eligible task and updates its scheduling/result state.

Where QCTNH participates

QCTNH supplies an external trigger path by calling native Joomla WebCron at meaningful times. It does not replace the task plugin or Scheduler selection logic. This separation is why a QCTNH wake-up can be successful even when a particular extension task later reports its own application failure.

Execution boundary

For How Joomla Scheduled Tasks Are Triggered, 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.