What Expired Laboratory Cleanup Removes

Expired Laboratory Cleanup removes known QCUL-owned temporary objects associated with laboratories/checkpoints that have reached the end of their lifecycle.

Typical owned cleanup scope

• Expired laboratory files/directories and access-gate/runtime artifacts.
• Run-specific copied database tables.
• Private package/checkpoint temporary artifacts associated with the expired run.
• Expired temporary production checkpoint data.

Evidence and ownership matter

QCUL uses run ownership/state to decide what it can remove. It does not treat every directory/table with a similar name as safely deletable; unowned-looking objects go to Orphan Scan reporting.

If cleanup cannot finish

The run/task reports attention and can continue in batches. Correct file/database privileges or resource constraints before deleting remaining objects manually.

Verify cleanup

After cleanup succeeds, the laboratory should no longer appear as active and its owned run-specific directories/tables/checkpoints should be gone. If qcul-style objects remain without an owning run, use Orphan Scan to report them and investigate ownership before manual deletion.

Scheduled-task verification

After changing or repairing What Expired Laboratory Cleanup Removes, 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.