Understanding Recent Activity Event Types and Messages

Recent Activity records QCTNH lifecycle events locally so administrators can reconstruct registration, synchronization, origin-protection, and pause/resume decisions.

Common event families

EventMeaning
registeredQuantaCade registration and WebCron readiness succeeded.
register failedRegistration did not complete; the message/context records a sanitized reason.
webcron not readyLocal native WebCron preparation failed.
webcron synced / sync failedA Joomla WebCron credential/configuration change was or was not synchronized.
service paused / service resumedAdministrator service-state transition.
service pause/resume sync failedLocal state changed, but the remote synchronization did not complete.
origin mismatch ignoredA different hostname/path was detected and automatic identity rotation was blocked.
origin changed confirmedTest Connection explicitly adopted a real new origin and created a new identity.

Message limits

Local history stores an event key, level, message (trimmed to 500 characters), optional JSON context, and UTC creation time. The Dashboard displays the latest 10 rows in site time.

Time and lock context

Understanding Recent Activity Event Types and Messages depends on current scheduler timestamps and Joomla’s timeout-derived lock threshold. A lock is not classified only by whether it exists; QCTNH compares its age with the Scheduler timeout (with a safety minimum) to distinguish recent active work from a soft/stale condition.

This is why changing clocks, restoring an older database, or interrupting a long-running task can make health look surprising until you inspect the underlying timestamps and process state.


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.