Which Scheduled Tasks QCTNH Considers Eligible
For health and next-due calculations, QCTNH considers only enabled, web-runnable Joomla Scheduled Tasks whose routine is currently available and whose next execution time is known.
Eligibility filter
| Rule | Required for QCTNH web-runnable calculations |
|---|---|
| Task state | state = 1 (enabled). |
| CLI exclusivity | cli_exclusive = 0. |
| Schedule | next_execution must not be NULL. |
| Routine availability | The task type must appear in Joomla Scheduler’s current TaskOption list. |
What is counted separately
Enabled CLI-exclusive tasks with a next execution time are counted in the Dashboard’s CLI-only Tasks field but are not included in due/next calculations for WebCron.
Why the filter is strict
The external service should only wake Joomla for work that the registered native WebCron transport can reasonably execute. Counting disabled, orphaned, or CLI-only work as WebCron backlog would create misleading “due” conditions.
How this affects eligibility
The behavior in Which Scheduled Tasks QCTNH Considers Eligible feeds QCTNH’s eligibility snapshot rather than bypassing Joomla. An ordinary web-runnable candidate must be enabled, not CLI-exclusive, have a non-null next execution time, and correspond to a task routine Joomla currently knows. Those filters prevent deleted/orphaned task types and CLI-only workloads from being advertised as work the WebCron path can perform.
When a task seems missing from QCTNH’s due/next-due view, inspect those eligibility conditions before changing service timing. Maximum Scheduler Delay cannot make an ineligible row executable.
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.