How Joomla Web Cron Works
Joomla Web Cron lets an external HTTP scheduler trigger Joomla's Scheduled Tasks system without requiring shell access. Joomla still stores the individual task records, execution rules, priorities, and task-specific settings. Web Cron supplies an execution opportunity; Joomla decides which enabled tasks are due.
Web Cron separates the trigger from the task definitions
Scheduled Tasks are managed inside Joomla under System → Manage → Scheduled Tasks. Web Cron is configured globally in the Scheduled Tasks options. When enabled and saved with the required key or hash, Joomla provides a Webcron link that an external service can request.
The external service does not need to know the details of every Joomla task. It calls the protected scheduler endpoint; Joomla evaluates its own task records.
The external requester controls trigger opportunities
A web-cron provider, monitoring platform, or other trusted HTTP scheduler requests the generated URL on a cadence you configure outside Joomla. That makes Web Cron different from Lazy Scheduler, which depends on normal site traffic, and from server cron with Joomla CLI, which starts a command-line process.
The external request frequency should be frequent enough to service the site's shortest important task interval, but calling the endpoint more often does not mean every task runs on every request.
Joomla's key protects the trigger URL
Joomla documentation describes Web Cron as disabled by default and requiring a hash when enabled. After the configuration is saved, Joomla displays a Webcron link URL to copy.
Treat that URL as a credential. Do not publish it in documentation, screenshots, public tickets, analytics notes, or source repositories. Give it only to the trusted system that needs to invoke the scheduler. If the secret is exposed, replace it using the controls available in the installed Joomla version.
Understand what a successful HTTP request proves
A successful request proves the external service reached the Web Cron endpoint; it does not automatically prove a particular task was due or completed successfully. The task can still be disabled, not yet due, misconfigured, timed out, or fail inside its own code.
For that reason, verify both layers: the delivery of the Web Cron request and the Joomla task execution result.
Verify Web Cron in practice
- Choose a safe scheduled task and run it manually first.
- Confirm the intended result.
- Allow the task to become due again.
- Let the external service request the Web Cron URL.
- Check Last Run or Execution History where available.
- Verify the actual task outcome.
If manual execution works but Web Cron does not, investigate the external request, secret URL, HTTP response, firewall/CDN rules, and scheduler configuration before changing the task itself.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.