QCTNH Dashboard Field Reference
The Dashboard combines service controls, scheduler timing, native WebCron readiness, lock counts, connectivity, and recent events in one operational view.
Top metrics
| Field | Meaning |
|---|---|
| Connected / Not Connected | Whether local identity, origin, native WebCron readiness/key hash, and remote registration are currently synchronized enough to treat the site as registered. |
| Scheduler Health | Healthy, Working, Attention, Due, or Error from scheduler snapshot/lock state. |
| Maximum Delay | Current selected fallback scheduler delay (5/10/15/30/60 minutes). |
| Oldest Due Task / Next Eligible Task | Timing summary chosen according to whether eligible work is already overdue. |
| QuantaCade Contact | Last successful broader service communication; frontend heartbeat shown separately. |
Health card fields
| Field | Meaning |
|---|---|
| Service | Enabled/paused state of free QuantaCade wake-up service. |
| Due Tasks | Count of currently due, enabled, web-runnable, recognized task rows. |
| Active Locks | Recent locks newer than Joomla Scheduler timeout threshold. |
| Soft / Stale Locks | Locks older than the timeout-derived threshold. |
| CLI-only Tasks | Enabled tasks marked CLI-exclusive and therefore excluded from WebCron. |
| Execution | Execution transport/summary; current transport is Joomla WebCron. |
| WebCron | Native Joomla WebCron readiness. |
| Health Endpoint | Operational service/health endpoint information exposed by the current UI. |
Actions
Service settings provide Maximum Scheduler Delay, the enable checkbox, Test Connection, Check WebCron, and Save. Recent Activity lists the latest 10 local history events in Joomla site time.
Architecture context
QCTNH Dashboard Field Reference belongs to the 2.0.3 native-WebCron architecture. QCTNH’s local component/plugin produces scheduler state and authenticated check-ins; the central service stores the validated endpoint/credential and schedules work; the worker calls Joomla WebCron; Joomla selects and runs the task.
This separation is useful when reading reference behavior because not every value is owned by the same layer. Task recurrence/locks belong to Joomla, wake-up timing belongs to the service, and identity/origin protection spans the local and central registration 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.