QCTNH Uninstall and QuantaCade Deregistration Lifecycle

Uninstall removes the local QCTNH extension and attempts to deregister the installation from QuantaCade, but a network/service failure does not block Joomla from completing the uninstall.

Uninstall lifecycle

  1. Use Joomla’s normal Extensions management workflow to uninstall the complete QCTNH package.
  2. The package/component uninstall path calls the service deregistration routine while the local identity is still available.
  3. If QuantaCade is reachable, the registered service entry can be retired.
  4. If it is unreachable, uninstall continues rather than trapping Joomla in a half-uninstalled state.

Joomla scheduling after uninstall

QCTNH is not Joomla Scheduler itself. Existing Joomla Scheduled Tasks remain owned by Joomla/their extensions. However, you lose the QuantaCade external wake-up and QCTNH health visibility, so ensure another trigger (traffic/Lazy Scheduler/server cron) meets your timing requirements.

Reinstall later

A future reinstall may create/restore service identity according to the local data/package state and will prepare native WebCron again. Verify Connected and origin after reinstall rather than assuming the previous remote registration is still authoritative.

Current vs legacy behavior

For QCTNH Uninstall and QuantaCade Deregistration Lifecycle, treat 2.0.3 behavior as authoritative over older QCTNH descriptions. The retired round-trip test task/direct-nudge execution model is not the current worker path. Native Joomla WebCron is the execution transport and the worker no longer requires a QCTNH callback/status preflight before each wake-up.

Compatibility endpoints/tables may still exist in source for safe upgrades or historical operations; their presence does not make them the primary customer workflow.

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.