How QCTNH Filters Currently Available Task Routines

QCTNH cross-checks scheduler rows against Joomla’s currently registered TaskOption routines so stale database rows do not create false due-task signals.

How active routines are discovered

QCTNH boots com_scheduler and asks SchedulerHelper::getTaskOptions() for the current routine options. Each option’s routine ID is collected into the allowed task-type list.

How the list is applied

When active routine IDs exist, QCTNH adds a type IN (...) filter to its web-runnable scheduler snapshot. A row whose plugin/routine is no longer registered does not contribute to due counts or next-due timing.

Discovery failure

If Joomla cannot provide TaskOptions, QCTNH does not pretend the queue is healthy. The snapshot becomes Error with a sanitized “Task routine discovery failed” message.

Use Joomla’s own evidence

When validating How QCTNH Filters Currently Available Task Routines, compare QCTNH with Joomla’s Scheduled Tasks screen. The database next_execution, task enabled state, CLI-exclusive flag, registered task routine, and lock state are the facts QCTNH uses. If Joomla itself shows a task disabled, locked, or no longer backed by a routine, QCTNH should not pretend it is a normal WebCron candidate.

This source-first comparison is especially useful after uninstalling or upgrading an extension that previously registered Scheduled Tasks.

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.