How to View Joomla Scheduled Task Execution History
Joomla Scheduled Task Execution History gives administrators a record of past scheduler runs. Use it to answer three practical questions: did the task run, when did it run, and did Joomla record that execution as successful or failed?
Confirm your Joomla version provides Execution History
The Scheduled Tasks Execution History view is available in current Joomla releases that include this scheduler feature. If your installation does not show the control described below, confirm the exact Joomla version before assuming the history is missing because of a configuration problem.
Open the history view
- Sign in to Joomla Administrator.
- Go to System → Manage → Scheduled Tasks.
- Select Execution History from the toolbar.
- Locate the task you want to investigate.
The history is separate from the task edit form; it summarizes executions rather than changing the task's schedule or parameters.
Read the execution details together
Review the task title and type along with execution count, last run time, duration, exit result, next execution information, and internal identifiers shown by the view. A recent run with an error result means the scheduler reached the task; an overdue task with no recent run points more strongly toward the trigger or due-state evaluation.
Do not diagnose from the exit value alone. Duration and timestamp often explain whether the failure is associated with a timeout, a specific cron invocation, or another system event.
Correlate a failed run with logs
Use the recorded execution time to inspect Joomla, PHP, web-server, database, cron, and extension-specific logs. The history view is a diagnostic index; detailed exceptions may live elsewhere.
When several runs fail, compare their timestamps and durations. A repeatable pattern is usually more useful than one isolated error.
Verify successful runs by their actual outcome
A scheduler success should be followed by a business-level check. Confirm that the cleanup occurred, message was sent, import completed, cache was processed, or other expected work actually happened. This matters especially for tasks that call external services or process work in stages.
Use history to verify reliability over time
Review several successive executions after a fix. Consistent run times, reasonable durations, successful results, and the expected real-world outcome provide evidence that both the task and its automatic trigger are 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.