How to Configure a Server Cron Job for Joomla Scheduled Tasks

Confirm command-line access and Joomla's scheduler commands

Joomla provides command-line scheduler commands such as scheduler:list and scheduler:run. Before creating cron, use the installed site's CLI help to confirm the syntax available on that Joomla version.

From the Joomla installation's CLI environment, a typical pattern is:

php cli/joomla.php scheduler:list
php cli/joomla.php scheduler:run --help

Do not put an untested command into cron. First make sure the PHP CLI binary can load the site and Joomla can see the scheduled tasks.

Build the cron command with absolute paths

Cron often runs with a minimal environment and a different working directory from your interactive shell. Use the hosting provider's correct PHP CLI executable and the absolute path to Joomla's cli/joomla.php.

For example, the structure may look like:

/usr/bin/php /home/account/public_html/cli/joomla.php scheduler:run --all

The paths above are examples only. Discover the real PHP and Joomla paths on your server. Use scheduler:run --help on the installed version before choosing options such as running all due tasks or a specific task ID.

Choose a cron frequency that matches the workload

The cron schedule supplies opportunities for Joomla to evaluate or run scheduled work; individual Joomla tasks retain their own execution rules. Run cron often enough to service the shortest important interval without launching it needlessly.

Consider task duration and server resources. If scheduled work can take longer than the cron interval, avoid creating uncontrolled overlapping processes. Hosting limits, PHP CLI settings, database load, and external API limits can all affect a sensible cadence.

Capture output while you are testing

During setup, retain standard output and errors in a protected log or use the hosting provider's cron logging. A command that works interactively can fail under cron because it uses a different PHP binary, PHP configuration, PATH, permissions, user account, or environment.

Do not embed Joomla Administrator passwords in the cron command. Joomla CLI operates in the context of the site installation and does not require an Administrator login password on the command line.

Verify the first automatic run

1. Manually run the exact command cron will use.
2. Confirm Joomla reports the expected scheduler behavior.
3. Save the cron entry.
4. Wait for cron itself to invoke the command.
5. Review the cron output or hosting log.
6. Check Joomla's Last Run information or Execution History where available.
7. Verify the real-world result of at least one due task.

A successful manual CLI run proves the command works in that shell. Only a later cron-triggered run proves the automation environment is configured correctly.

Troubleshoot cron separately from the task

If a task succeeds with Joomla's manual Test Task but fails under cron, inspect the cron command, PHP CLI version, filesystem permissions, environment, and logs. If the cron command reaches Joomla but one task fails, focus on that task's configuration and execution error.

Once server cron is the intended trigger, document that choice and avoid enabling additional trigger methods merely as backups unless you have a specific reason and understand the resulting execution behavior.