Retrying Removal After a Failed Cleanup

When cleanup cannot remove every QCUL-owned laboratory object, the run enters a removal-attention state so cleanup can be retried instead of falsely claiming success.

Location: Joomla Administrator → Components → QC Update Laboratory → Laboratory.

Step-by-step procedure

1. Open the Laboratory workspace and read the Removal needs attention message.
2. Correct the underlying problem where possible: filesystem permissions/open handles, database privileges, or owned objects that could not be removed.
3. Select Retry Removal.
4. Allow cleanup to continue from persisted state.
5. If cleanup repeatedly fails, preserve the error details before manually inspecting qcul-labs directories or qcul_ database objects.

Preserve evidence before manual cleanup

If Retry Removal continues failing, capture the exact QCUL message and identify whether the obstruction is filesystem, database, or hosting-level. Manual deletion should be a controlled last resort because QCUL needs to distinguish owned run objects from unrelated data.

Safety check before update testing

Before relying on Retrying Removal After a Failed Cleanup, confirm the private copy still shows laboratory identity, its access gate works, and ordinary browsing stays inside the lab rather than silently using production. The cloned site contains production-derived data, so a laboratory that is not demonstrably isolated should be repaired or refreshed before any update rehearsal.

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.