QCTNH Local History, Operations, and Nonce Tables Reference
QCTNH maintains small local operational tables for history, legacy/current operation tracking, and nonce replay protection; these support diagnostics/security and are not customer-content stores.
Local tables
| Table | Purpose |
|---|---|
#__qctasknudge_history | Event key, level, message, optional JSON context, and UTC creation time used by Recent Activity. |
#__qctasknudge_operations | Operation IDs/status/task metadata/timestamps retained for operational compatibility/history; current direct worker does not rely on this table as a private task executor. |
#__qctasknudge_nonces | Recently seen nonces used to reject replayed authenticated QCTNH requests. |
History details
Messages are bounded (up to the current field limit) and the Dashboard shows the latest 10 rows converted from stored UTC to Joomla site time. Context is operational JSON, not a copy of arbitrary site content.
Nonce cleanup
Incoming signed-message verification records nonces and removes sufficiently old nonce rows; duplicate recent nonces fail authentication. Administrators normally do not need to edit these tables manually.
Operational limits are deliberate
The constraints documented in QCTNH Local History, Operations, and Nonce Tables Reference—public origin, standard ports, exact Joomla route, no CLI-only execution through WebCron, bounded retries, and no automatic stale-lock clearing—are safety/reliability design choices rather than missing configuration switches.
A workload outside those boundaries should use the appropriate Joomla/server mechanism instead of trying to make QCTNH bypass the task author’s or network’s execution model.
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.