Understanding QuantaCade Contact and Frontend Heartbeat Times

The last QuantaCade contact and frontend heartbeat timestamps answer different questions: “when did service communication last succeed?” and “when did normal site traffic last send the throttled browser heartbeat?”

QuantaCade Contact

Updated after successful registration/check-in/service synchronization and when a valid signed incoming service request is verified. It is the broader service-contact indicator.

Frontend heartbeat

Updated only after a successful frontend_heartbeat check-in. The local throttle allows this roughly once every six hours, so it is expected to be much less frequent than page views.

Use them together

Recent QuantaCade Contact with an older heartbeat can be perfectly healthy if communication is happening through task changes or WebCron completion. If both remain “Not yet” after Test Connection and normal traffic, investigate registration/networking.

Interpret the state with precedence

For Understanding QuantaCade Contact and Frontend Heartbeat Times, 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.