How to Run a Joomla Scheduled Task Manually

Open Joomla Scheduled Tasks and identify the task

1. Sign in to the Joomla Administrator.
2. Go to System → Manage → Scheduled Tasks.
3. Find the task you want to test. Confirm its title, task type, published state, interval, and last-run information before executing it.

If the task was created by a third-party extension, make sure that extension and its task plugin are enabled. A task definition can appear in the list even when another dependency prevents useful work from completing.

Review what the task will do before running it

Open the task and review its parameters. This matters most for tasks that send messages, delete expired records, process queues, create files, synchronize remote systems, or perform large batches.

• Use a test recipient or test environment when the task can send email or notifications.
• Back up important data before testing a destructive maintenance task.
• Check API credentials, paths, storage destinations, and other task-specific configuration.
• If the task processes items in batches, understand whether one manual execution processes everything or only one batch.

Saving a task and manually executing it are separate actions. Save any configuration changes first so the execution uses the settings you expect.

Run the task manually

From the Scheduled Tasks interface, use the task's manual execution action. Depending on the Joomla version and screen layout, this may be labelled Run, Run Test, or be available from the toolbar after selecting the task.

1. Select or open the intended task.
2. Start the manual execution.
3. Wait for Joomla to report the result. Do not repeatedly click the run action while the first execution is still in progress.
4. Read the completion message carefully. A successful scheduler launch does not always mean the task's business operation succeeded; an extension may report its own warning or error in the task output or logs.

If the task takes longer than the browser request can remain open, the manual test may time out even though part of the task executed. Check the task's last-run information and relevant logs before running it again.

Verify the result instead of relying only on the success message

Confirm the task changed the system in the way it was supposed to. For example, verify that queued records were processed, generated files exist, expired records were removed, remote data synchronized, or the expected test email was received.

Also review the task's status and execution information in Joomla. If the extension maintains its own log, check that as well. For server-level failures, inspect Joomla and PHP error logs.

If the task runs manually but not automatically

A successful manual run is useful because it separates the task itself from the scheduling mechanism. If manual execution works but automatic execution does not, focus on how the scheduler is being triggered.

• Confirm the task is published and its execution interval is correct.
• Check Joomla's Scheduled Tasks configuration and the execution method in use.
• If you use a server cron job, verify the cron command, PHP executable, working environment, and hosting restrictions.
• If you use the web/lazy scheduler, remember that it depends on site traffic and the configured scheduler behavior.
• Check whether a previous execution is stuck or whether the task's locking/concurrency rules prevent another run.

If manual execution also fails, troubleshoot the task's own configuration, extension dependencies, PHP/server requirements, permissions, network access, and error logs first.