Reading the Scheduler Health Metric
Scheduler Health summarizes the web-runnable Joomla queue using a fixed priority: active work, stale locks, overdue work, then healthy idle/future work.
Health priority
| Health | Trigger |
|---|---|
| Working | At least one enabled task has an active lock newer than the Scheduler timeout threshold. |
| Attention | No active lock, but at least one eligible web-runnable task has a stale/soft lock. |
| Due | No active/stale lock condition takes priority and one or more eligible tasks are due. |
| Healthy | No active/stale locks and no eligible tasks are overdue. |
| Error | Task routine discovery or scheduler snapshot/database work failed. |
Read the counts with the label
The summary card also shows due and active-lock counts. For example, Working with due tasks can simply mean Joomla is currently processing work; Due with zero active locks means work is waiting rather than visibly running.
Change one variable at a time
When adjusting Reading the Scheduler Health Metric, make a single deliberate change, Save where required, and then read the resulting Dashboard/Recent Activity state. This avoids confusing a timing-setting change with an unrelated WebCron or task failure.
Use Check WebCron when you only need local readiness confirmation. Reserve Test Connection for a full service-registration probe, because its real WebCron request can give Joomla one eligible task-execution opportunity.
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.