How to Determine Whether Joomla Scheduled Tasks Are Actually Running
Start with the Scheduled Tasks list
Open System → Manage → Scheduled Tasks and identify the task you want to verify. Check that it is enabled and review its Last Run and Next Execution information. A configured schedule alone is not proof of execution; you need evidence that Joomla has actually run the task.
Use Execution History where available
Joomla 5.3 and later provides Scheduled Tasks Execution History. Open the Execution History view and locate the task. Review the Last Run Date, Duration, Times Executed, and Last Exit Code. Joomla documents Executed: 0 as a successful execution, while other values indicate an error or failure.
Verify the task's real-world result
A successful scheduler record is important, but also confirm what the task was supposed to accomplish. Check the updated records, generated files, notifications, cleanup result, external synchronization, or other observable outcome. This catches cases where the scheduler ran but the task's business operation did not produce the expected result.
Identify the trigger mechanism
Determine whether the site uses server cron/CLI, Web Cron, or Lazy Scheduler. Each mechanism provides opportunities for Joomla's scheduler to process due tasks. Verify the intended mechanism is actually active instead of assuming that creating a task automatically creates a server cron job.
Compare manual and automatic execution
Run a safe task manually when appropriate. If manual execution succeeds but no automatic runs appear, focus on the trigger, schedule, and automatic runtime environment. If both manual and automatic runs fail, focus on the task plugin, configuration, dependencies, logs, and resource limits.
Check logs around the expected run time
Review Joomla, PHP, web-server, cron, and extension-specific logs around the time the task should have run. Server cron services often have their own output or job history. Matching timestamps can prove whether the scheduler was invoked and reveal failures that the task list summarizes only as an exit code.
Watch more than one scheduled cycle
For recurring work, verify successive unattended runs rather than declaring the scheduler healthy after one test. Consistent execution times, successful history entries, and correct real-world outcomes provide much stronger evidence that the Joomla scheduling path is operating reliably.
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.