Troubleshooting Missing Recent Activity or Frontend Heartbeat Evidence
Missing Recent Activity or frontend-heartbeat evidence can be normal in some traffic patterns, but persistent absence after manual operations helps identify local plugin/history/check-in problems.
Recent Activity expectations
Dashboard displays only the latest 10 local history rows. A quiet site with no recent changes may show older events; a database cleanup/restore can also alter history independently of service state.
Frontend heartbeat expectations
The heartbeat is injected on normal frontend HTML responses when the service is enabled and is locally throttled to roughly once every six hours. It is not expected on every page load, administrator request, API response, or cross-site request.
Diagnose
- Confirm the QCTNH system plugin is enabled.
- Load a normal frontend page from the same site/origin and verify browser/network/security rules are not blocking the QCTNH AJAX heartbeat.
- Check the Dashboard after the throttle window rather than expecting immediate repetition.
- Use Test Connection or service Save to generate independent operational activity; if those also produce no history, inspect database writes/component errors.
- Remember that successful worker WebCron completion can update QuantaCade Contact even when no visitor heartbeat occurs.
Preserve the failure evidence
Before attempting a repair for Troubleshooting Missing Recent Activity or Frontend Heartbeat Evidence, record the HTTP/status message, Scheduler Health, due/lock counts, WebCron state, QuantaCade Contact, and Recent Activity timestamp. For lock/task problems, also capture the owning Scheduled Task title/type and extension log.
That evidence lets you verify the fix and avoids converting a precise 401/403/404/task_failed condition into an ambiguous “it works now” report.
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.