Oldest Due Task vs Next Eligible Task

The same Dashboard metric changes label depending on whether eligible WebCron work is already overdue.

Oldest Due Task

When Due Tasks > 0, the label becomes Oldest Due Task. The displayed time is the earliest eligible next_execution; the note shows how many web-runnable tasks are overdue.

Next Eligible Task

When nothing is overdue, the metric becomes Next Eligible Task and shows the earliest future eligible execution time. If no eligible known time exists, it shows Waiting / unknown.

Scope reminder

Both views exclude disabled, CLI-only, orphaned/unavailable routine rows, and rows without next_execution. The metric describes the queue QCTNH can support through Joomla WebCron.

Interpreting a stable result

After using Oldest Due Task vs Next Eligible Task, a stable QCTNH system should settle into a coherent set of indicators: native WebCron ready, service state matching your choice, scheduler health consistent with current locks/due work, and recent service contact when registration/check-ins succeed.

Temporary transitions are normal—for example, Working while a task lock is active or Due while queued work waits. The goal is not to force every metric to green at every instant; it is for the metrics to accurately describe Joomla’s real scheduler state.

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.