What Operational Data QCTNH Sends to QuantaCade

QCTNH sends only the operational information needed to register the site, schedule appropriate wake-ups, authenticate service communication, and understand Joomla Scheduler timing.

Registration/check-in data

DataWhy it is used
Installation UUIDStable service-installation identity for the registered site.
Site originBinds the identity to the intended public Joomla origin and protects against clone takeover.
Native Joomla WebCron endpoint and keyLets the worker make an authenticated Joomla WebCron request when wake-up is due.
QCTNH service secret / signed message materialAuthenticates QCTNH↔QuantaCade service messages; stored encrypted rather than shown publicly.
Maximum Scheduler Delay / service enabled stateControls wake-up scheduling policy.
QCTNH and Joomla versionsOperational compatibility/support context.
next_due, next_due_known, due_countLets QuantaCade schedule useful wake-ups instead of fixed high-frequency polling.

Later scheduler snapshots

Task-state changes, WebCron completion, frontend heartbeat, and manual operations can refresh the aggregate next-due/due-count timing. QCTNH does not need visitor page content to make those scheduling decisions.

Secrets and diagnostics

When troubleshooting What Operational Data QCTNH Sends to QuantaCade, prefer status codes, readiness states, hashes/“matches” indicators, and sanitized activity messages over copying raw secrets. The Joomla WebCron key and QCTNH service credential are operational credentials, not ordinary configuration text for screenshots or public discussion.

If compromise is suspected, rotate the WebCron key and resynchronize rather than trying to keep an exposed credential active.


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.