Understanding Known, Unknown, and Waiting Next-Due Status
Next-due information can be known, unknown, or effectively waiting depending on whether QCTNH can identify an eligible web-runnable task with a scheduled execution time.
Status meanings
| Display/state | Meaning |
|---|---|
| Known future time | An eligible task exists and QCTNH knows its earliest next_execution. |
| Known overdue time | Eligible due work exists; the Dashboard labels the metric Oldest Due Task. |
| Waiting / unknown | No eligible next execution is currently available to report. This can be normal on an idle queue. |
Central significance
A known future value allows precise schedule-aware polling. Unknown timing makes the service rely on fallback/safety timing instead of targeting a specific due moment.
Do not “fix” the metric directly
The correct response to Understanding Known, Unknown, and Waiting Next-Due Status is to resolve the underlying Joomla state, not edit QCTNH’s displayed value. Due counts change when Joomla advances task schedules; locks change when tasks start/finish or are safely recovered; contact times change after authenticated service communication.
Manual database edits to make a Dashboard number look better can hide the real scheduler problem and are not part of normal QCTNH operation.
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.