Why QCTNH Does Not Create Its Own Joomla Scheduled Task

QCTNH intentionally does not create its own Joomla Scheduled Task because its job is to wake and observe Joomla’s existing scheduler, not add another workload to the queue it is trying to trigger.

Current architecture

  1. Extensions register their own Joomla Scheduled Tasks.
  2. QCTNH snapshots eligible/due/lock state from Joomla Scheduler.
  3. QuantaCade calls the site’s native Joomla WebCron endpoint when wake-up is useful.
  4. Joomla Scheduler chooses the next eligible task according to its own rules.
  5. After WebCron completes, QCTNH can check in fresh timing for the next wake-up.

Benefits

  • No circular dependency on a QCTNH task that itself needs Scheduler to run.
  • No need to prioritize a proprietary “nudge” task ahead of real work.
  • Cleaner compatibility with Joomla’s native queue/locking behavior.
  • CLI-only and unavailable/orphaned routines remain naturally outside the WebCron-eligible set.

Reference verification

When checking Why QCTNH Does Not Create Its Own Joomla Scheduled Task on a live site, prefer observable 2.0.3 state: QCTNH Dashboard/Status, Joomla Scheduler and Schedule Runner configuration, Recent Activity, and owning-extension logs. Internal tables/endpoints are reference material and should not be edited/called casually just because they exist.

This keeps normal administration on supported UI paths while still giving advanced administrators enough detail to understand what the product is doing.

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.