How QCTNH Determines Which Tasks Are Due

A task contributes to QCTNH’s Due Tasks count only when it is enabled, web-runnable, currently registered as a valid task routine, has a known next execution, and that time has arrived or passed.

Due formula

Conceptually, QCTNH applies: enabled + not CLI-only + active routine + next_execution present + next_execution ≤ now.

Common reasons a task is not counted

  • The task is disabled.
  • It is CLI-exclusive.
  • Its task plugin/routine is no longer registered.
  • Its next_execution is NULL.
  • Its next execution time is still in the future.

Use Due Tasks as a WebCron backlog indicator

The count is intentionally scoped to the queue QCTNH can help wake through WebCron. It is not a count of every row in Joomla’s Scheduler table.

Execution boundary

For How QCTNH Determines Which Tasks Are Due, remember that one WebCron request is an execution opportunity, not a command to run a named task. QCTNH never sends a task ID to force selection. Joomla receives its normal System - Schedule Runner request, applies its queue/lock/recurrence rules, and returns the result of the work it chose.

This design is why QCTNH can work with Scheduled Tasks from many extensions without knowing their business logic. It also explains why a task-specific error belongs first to the owning extension even when QCTNH successfully delivered the WebCron request.

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.