How QCTNH Uses a Task's next_execution Time

QCTNH uses Joomla’s stored next_execution timestamp as the key timing signal for deciding whether web-runnable work is due and when the next eligible task is expected.

Due calculation

For an eligible task, QCTNH treats it as due when next_execution <= current UTC time. The Due Tasks count is the number of eligible rows meeting that condition.

Next eligible calculation

Among eligible rows, QCTNH orders by next_execution ascending and reports the earliest value. The administrator UI converts stored UTC timestamps exactly once into the Joomla-configured site timezone for display.

Why timing can be unknown

If there is no eligible task with a non-NULL next_execution, QCTNH reports the next due time as unknown/waiting. That is not automatically an error; it can simply mean there is no schedulable WebCron work to predict.

Timing consequence

The scheduler rule described in How QCTNH Uses a Task's next_execution Time also affects when QuantaCade should wake the site. QCTNH reports aggregate next_due, whether that value is known, and a due count. When an exact future time is known, the central service can sleep toward that point instead of generating fixed high-frequency traffic.

If timing is unknown, QCTNH falls back to the configured Maximum Scheduler Delay and safety rechecks. Therefore a timing problem should be diagnosed from the scheduler snapshot first, not by assuming the service is simply a cron request every N minutes.

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.