Understanding the Execution, WebCron, and Health Endpoint Fields

The Execution, WebCron, and Health Endpoint fields describe different layers; reading them together avoids assuming that the QCTNH control URL is the current task-execution path.

Execution

Execution: Joomla WebCron is the current 2.0.3 transport. QuantaCade wakes the exact registered native Joomla WebCron route.

WebCron

Ready means Schedule Runner is enabled, Joomla WebCron is enabled, and a key exists. Needs attention means at least one of those local prerequisites is missing.

Health Endpoint

The displayed endpoint is QCTNH’s control/AJAX endpoint under the site. It supports signed verify/status/sync compatibility and the same-site browser heartbeat. The current direct-WebCron worker architecture does not call this endpoint before each wake-up; it calls Joomla WebCron directly.

What the setting cannot override

Understanding the Execution, WebCron, and Health Endpoint Fields does not override Joomla task recurrence, task state, CLI exclusivity, locks, or extension-specific failures. QCTNH can change when an external wake-up is useful and can show the current scheduler condition, but Joomla still decides whether a task is eligible and what happens during execution.

If the Dashboard value looks correct yet a specific workload remains wrong, move the investigation to Joomla Scheduled Tasks and the owning extension rather than repeatedly changing QCTNH service settings.

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.