QCTNH Registration Lifecycle Reference

QCTNH registration has a defined lifecycle: local identity creation, native WebCron preparation, public registration/probe, ongoing check-ins, optional explicit origin rotation, and uninstall deregistration.

Lifecycle

  1. Install/first run: create installation UUID/service secret, enable/prepare Joomla WebCron, build native route.
  2. Register: send identity/origin/endpoint/key/version/timing data; QuantaCade validates target and performs a real WebCron probe.
  3. Connected operation: local task changes, WebCron completion, frontend heartbeat, and manual actions can refresh scheduling data.
  4. Credential drift: changed WebCron configuration is synchronized; local stored key hash must match current key for registered state.
  5. Origin change: automatic mismatch is blocked; Test Connection explicitly rotates identity for an intentional move.
  6. Uninstall: QCTNH attempts remote deregistration, but local uninstall is allowed to finish even if QuantaCade is unreachable.

Registration is service enrollment, not licensing

There is no paid entitlement or activation tier in this lifecycle. The registration exists so the service can securely wake the correct Joomla WebCron endpoint.

Reference verification

When checking QCTNH Registration Lifecycle Reference on a live site, prefer observable 2.0.3 state: QCTNH Dashboard/Status, Joomla Scheduler and Schedule Runner configuration, Recent Activity, and owning-extension logs. Internal tables/endpoints are reference material and should not be edited/called casually just because they exist.

This keeps normal administration on supported UI paths while still giving advanced administrators enough detail to understand what the product is doing.

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.