Pausing and Resuming Laboratory Processing
QCUL is designed so long file/database operations can pause between bounded requests and resume from saved state instead of restarting completed work.
Location: Joomla Administrator → Components → QC Update Laboratory → Laboratory.
Step-by-step procedure
- If the browser is closed or the operation stops after a completed batch, reopen QC Update Laboratory → Laboratory.
- Read the saved state/message instead of starting a second laboratory operation.
- Use the displayed Resume or continuation action when QCUL offers it.
- Keep the page open while subsequent bounded requests continue.
- If the same state repeats without progress, investigate the shown error and server limits rather than clicking the action repeatedly.
Why pausing is safe
The server owns the current run state, cursor, locks, hashes, progress, and operation identity. A browser request cannot simply declare the run complete. Closing the page stops new AJAX requests after the current server request finishes; it does not erase completed batches.
Avoid concurrent actions
A site-wide MySQL advisory lock and per-run locking protect heavy operations. Do not open multiple tabs and start competing create/refresh/test/push/rollback actions; let the active operation finish or enter a defined attention state first.
Safety check before update testing
Before relying on Pausing and Resuming Laboratory Processing, 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.