Default Schedules for the Three QCUL Tasks
QCUL provisions sensible default schedules for its three maintenance tasks while preserving legitimate administrator-selected schedules on existing canonical task rows.
Default schedules
| Task | Default |
|---|---|
| QC Update Laboratory Expired Laboratory Cleanup | Every 60 minutes |
| QC Update Laboratory Orphan Scan | Every 24 hours |
| QC Update Laboratory Production Safety Check | Every 24 hours |
Defaults are not forced forever
The integrity service repairs missing/invalid execution-rule containers, but it is intentionally written not to replace valid administrator-selected schedules or a deliberately unpublished canonical task. That means your operational policy can adjust cadence without QCUL resetting it on every check/update.
Choose cadence based on consequence
Hourly cleanup keeps expired temporary data moving out promptly. Daily orphan/safety scans are appropriate for background maintenance; run them more often only if you have a specific operational need and sufficient resources.
Scheduled-task verification
After changing or repairing Default Schedules for the Three QCUL 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.