How the Direct Joomla WebCron Wake-Up Path Works

The current 2.0.3 worker has one primary QuantaCade-to-site execution target: the exact native Joomla WebCron endpoint registered by the site.

Direct wake-up path

  1. The site registers its Joomla-generated WebCron base URL and key outbound to QuantaCade.
  2. The central worker selects a due registered site according to its stored next-poll schedule.
  3. The worker validates that the endpoint still resolves to public IP space and sends an HTTP GET to the registered URL with the Joomla WebCron key as hash.
  4. Joomla System - Schedule Runner receives the request and lets Joomla Scheduler choose/run an eligible task.
  5. After the request completes, the local QCTNH System plugin sends an outbound webcron_complete check-in when registration is valid, providing the fresh scheduler snapshot.

No task ID is sent

The registered endpoint explicitly excludes both hash and id. The worker appends only the secret hash at execution time. Task selection remains entirely inside Joomla.

Why the service can stay quiet

The mechanism in How the Direct Joomla WebCron Wake-Up Path Works is designed to minimize needless traffic. Once QuantaCade has a trustworthy future next_due, it can schedule the next useful check near that time with small jitter and a bounded safety recheck rather than polling the Joomla site every few minutes indefinitely.

Fresh state after WebCron completion is especially valuable because it tells the worker whether more work remains due, a later future task is known, or the site can safely sleep.

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.