Understanding QCUL Scheduled Tasks
QCUL 1.01.14 registers three operational Joomla Scheduled Tasks for unattended lifecycle and safety maintenance; none of them installs an update to production.
Current task register
| Task | Default schedule | Purpose |
|---|---|---|
| QC Update Laboratory Expired Laboratory Cleanup | Every 60 minutes | Closes expired laboratory access, removes run-owned temporary tables/files in resumable batches, and records cleanup verification evidence. |
| QC Update Laboratory Orphan Scan | Every 24 hours | Reports unowned QCUL laboratory directories and run-prefixed database tables; 1.01.14 does not auto-delete unowned findings. |
| QC Update Laboratory Production Safety Check | Every 24 hours | Rechecks tested updates against current production and records whether the exact production push remains safe to offer. |
Joomla still has to run Scheduled Tasks
Task rows do nothing by themselves. Joomla Lazy Scheduler or a reliable server cron must actually trigger Joomla Scheduled Tasks. For production maintenance, server cron is usually the most predictable choice.
No automated production deployment
The tasks clean expired owned data, report orphans, and refresh production-safety status. Push to Production remains an explicit administrator action tied to a tested/reviewed item and protection choice.
Scheduled-task verification
After changing or repairing Understanding QCUL Scheduled Tasks, verify the canonical task row in System → Scheduled Tasks: enabled/disabled state, Last Execution, Next Execution, and Last Exit Code. Registration alone does not prove the maintenance routine runs; Joomla Scheduler still needs Lazy Scheduler or server cron to trigger due work.
Community Discussion
Want to compare update-testing workflows, share practical tips, or discuss how you use this QCUL feature? Visit the QC Update Laboratory Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.