Understanding QCTNH Scheduler Health States
QCTNH reduces several scheduler signals to five health states so an administrator can tell the difference between idle, actively working, overdue, stale-lock, and snapshot-error conditions.
Health-state precedence
| Priority | State | Condition |
|---|---|---|
| 1 | Working | Active lock exists. |
| 2 | Attention | No active lock, but an eligible stale/soft lock exists. |
| 3 | Due | No higher-priority lock condition and eligible tasks are overdue. |
| 4 | Healthy | No active/stale locks and no eligible overdue tasks. |
| Separate failure | Error | Snapshot/task-option discovery failed. |
Why precedence matters
A site can have due tasks while another task is currently running. Showing Working instead of Due prevents the Dashboard from implying “nothing is happening” when Joomla is visibly processing scheduler work. Likewise, Attention highlights stale-lock evidence before simply showing the overdue queue.
Interpret the state with precedence
For Understanding QCTNH Scheduler Health States, QCTNH’s health label is a summary, not the whole snapshot. Error conditions come from failed discovery/query operations; recent active locks produce Working; stale locks produce Attention; due eligible work produces Due when no lock state takes precedence; otherwise the result is Healthy.
Always read the individual Due Tasks, Active Locks, Soft / Stale Locks, CLI-only Tasks, and WebCron fields when diagnosing an unexpected label.
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.