How QCTNH Repairs WebCron Credential Drift

QCTNH detects WebCron credential drift and synchronizes the current Joomla endpoint/key rather than continuing to let the service call an obsolete credential.

Detection points

  • The component compares the stored registered WebCron-key hash with the current Schedule Runner key when determining whether it is truly registered.
  • The system plugin listens for Joomla com_scheduler configuration saves and calls the WebCron synchronization path.
  • Check WebCron/Test Connection also re-read and prepare the current native configuration.

Synchronization behavior

QCTNH sends the current native Joomla WebCron endpoint and key through the authenticated registration/synchronization path. QuantaCade validates the public origin/route before using it for future wake-ups. The key is not displayed as a public diagnostic value.

Verify repair

  • Dashboard returns to Connected.
  • WebCron reports ready.
  • Recent Activity shows a successful WebCron synchronization/registration rather than repeated sync failures.
  • A later worker wake-up reaches Joomla without 401/credential errors.

Finish the canonical URL first

Before applying How QCTNH Repairs WebCron Credential Drift, settle DNS, HTTPS, www/non-www policy, and Joomla base path. QCTNH registers an exact native WebCron endpoint whose scheme/host/path must correspond to the final site origin. Registering during an intermediate redirect state creates avoidable 301/302, TLS, or route failures.

After the public URL is stable, Check WebCron rebuilds the local native route and Test Connection confirms public reachability/identity.

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.