How QCTNH, Joomla Scheduled Tasks, and WebCron Fit Together

QCTNH, Joomla Scheduled Tasks, and Joomla WebCron are three layers of the same execution chain: QCTNH decides when to wake, WebCron provides the trigger, and Joomla chooses/runs the task.

Responsibility map

LayerResponsibility
Scheduled Task plugin/routineDefines what the job does.
Joomla Scheduler componentStores task rows, recurrence, next_execution, locks, state, and chooses the next eligible task.
System - Schedule RunnerExposes Joomla’s native WebCron trigger and validates the WebCron hash.
QCTNH local component/pluginMeasures scheduler state, prepares WebCron, reports next-due timing, maintains registration, and shows health.
QuantaCade Task Nudge serviceSchedules external wake-ups and calls the registered native Joomla WebCron endpoint when appropriate.

The important rule

QCTNH never turns “task X is due” into “run task X directly.” The remote service does not register a task ID in its wake-up URL. It calls the native WebCron route with the Joomla WebCron key, then Joomla applies its own queue/locking logic.

Verify the surrounding system

After applying the guidance in How QCTNH, Joomla Scheduled Tasks, and WebCron Fit Together, also confirm the Joomla side still behaves normally: Scheduled Tasks load in Joomla Administrator, task types from installed extensions are present, and the site can generate its native WebCron route. QCTNH should complement those facilities rather than replace them.

For quiet-site reliability, the final operational check is not simply “QCTNH is installed.” It is that the site has at least one eligible web-runnable task when appropriate, WebCron is ready, and the service connection can be tested from the intended public canonical URL.


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.