Why Orphaned Scheduled Task Rows Are Excluded

An orphaned Scheduler row is a database task whose routine is no longer available from Joomla’s registered task plugins; QCTNH excludes those rows from WebCron health calculations.

Why orphaned rows are misleading

A stale row can still be enabled and have a past next_execution, but if Joomla no longer exposes the associated routine it is not meaningful runnable work. Counting it would keep QCTNH in a permanent Due state and cause unnecessary wake-ups.

How QCTNH avoids the problem

The snapshot filters rows by the active TaskOption IDs discovered from Joomla Scheduler. Orphaned rows remain Joomla data to be investigated by the administrator, but they do not drive the QCTNH web-runnable queue.

If you suspect an orphan

  1. Open System → Scheduled Tasks and identify tasks whose owning extension/plugin was removed or disabled.
  2. Verify the task type is still offered by Joomla when creating/editing tasks.
  3. Remove or repair stale task rows using Joomla/extension-supported tools rather than editing the database blindly.

How this affects eligibility

The behavior in Why Orphaned Scheduled Task Rows Are Excluded 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.