What Happens During One Joomla WebCron Request

One native Joomla WebCron request is one Scheduler execution opportunity. QCTNH treats the response and post-run scheduler snapshot as signals for what should happen next.

Request lifecycle

  1. QuantaCade calls the registered native WebCron URL with Joomla’s WebCron hash.
  2. System - Schedule Runner validates the request and hands control to Joomla Scheduler.
  3. Joomla selects and runs an eligible due task according to its rules.
  4. The JSON response can indicate HTTP success while also indicating application/task success or failure.
  5. After the WebCron request completes, the QCTNH System plugin sends an outbound webcron_complete check-in with the fresh scheduler snapshot when the site is registered.
  6. If more work remains due, the worker can perform bounded follow-up WebCron calls.

HTTP success is not the same as task success

The central worker parses Joomla’s JSON success field. A 2xx WebCron response with success:false is recorded as task_failed, not as a transport failure.

Use Joomla’s own evidence

When validating What Happens During One Joomla WebCron Request, compare QCTNH with Joomla’s Scheduled Tasks screen. The database next_execution, task enabled state, CLI-exclusive flag, registered task routine, and lock state are the facts QCTNH uses. If Joomla itself shows a task disabled, locked, or no longer backed by a routine, QCTNH should not pretend it is a normal WebCron candidate.

This source-first comparison is especially useful after uninstalling or upgrading an extension that previously registered Scheduled Tasks.

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.