Understanding Connected and Not Connected Status

The Dashboard connection badge is stricter than a simple “registered flag”: QCTNH shows Connected only when the local identity, current origin, WebCron configuration, and stored WebCron-key hash still agree.

Connected requires all of these

• The component parameter registered is set.
• The stored registered origin is equivalent to the current Joomla origin.
• Joomla WebCron is ready: enabled Schedule Runner, enabled WebCron, non-empty key.
• The hash of the current Joomla WebCron key matches the hash saved at registration/synchronization.

Why Not Connected can be useful

A changed WebCron key, real migration, disabled Schedule Runner, or incomplete registration should invalidate the badge rather than leaving a false green state. Use Check WebCron first, then Test Connection if the local WebCron prerequisites are ready.

Use the Dashboard as a cross-check

The control or metric covered by Understanding Connected and Not Connected Status is most useful when read beside the other Dashboard evidence. Connected status alone does not prove a particular task is healthy, and a Due count alone does not prove the wake-up service is broken. Compare WebCron readiness, lock counts, next/oldest timing, QuantaCade Contact, and Recent Activity before drawing a conclusion.

That combined view usually tells you whether the next action belongs in Joomla Scheduler, QCTNH service configuration, networking/WebCron, or the extension that owns the failing task.

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.