Understanding the QCTNH Installation UUID and Service Credential
QCTNH identifies an installation with a random installation UUID plus a separate service credential; both are local operational identity data, not a license key.
Installation UUID
If installation_uuid is empty, QCTNH generates 16 random bytes and stores the 32-character hexadecimal value in component parameters. The UUID lets QuantaCade distinguish installations and preserve a registration across normal upgrades/restores on the same origin.
Service credential
QCTNH generates 32 random bytes and stores the 64-character hexadecimal service secret locally only after encrypting it with AES-256-GCM. The local encryption key is derived from Joomla’s site secret plus a QCTNH-specific context string.
Why there are two values
| Value | Purpose |
|---|---|
| Installation UUID | Stable installation identifier used in registration lookup. |
| Service secret | HMAC credential used to authenticate signed QCTNH↔QuantaCade service messages. |
| Joomla WebCron key | Separate Joomla-owned secret used only to authenticate native WebCron execution. |
Migration behavior
A deliberate origin adoption through Test Connection rotates both the installation UUID and service secret so the migrated site becomes a new service identity instead of silently hijacking the original registration.
Failure-safe scheduling
Understanding the QCTNH Installation UUID and Service Credential also sits inside bounded retry rules. A busy/ambiguous timeout can receive a short continuation, more-due work can receive a quick follow-up, while a task failure backs off instead of hammering the same failing workload. Unknown timing eventually falls back to Maximum Scheduler Delay/safety checks.
These distinctions are why Recent Activity and task/HTTP result codes matter: the worker does not treat every unsuccessful response as the same reason to retry.
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.