Resuming an Interrupted Laboratory Restore
A laboratory restore can stop between batches without losing already completed work; QCUL stores the cursor/state and offers a safe continuation path when the cause is recoverable.
Step-by-step procedure
- Read the saved laboratory state and error instead of starting another test.
- If the UI offers a resume/continuation action, select it once.
- Keep the page open while QCUL continues from its saved database/file cursor.
- If the same signature repeats without progress, stop retrying and correct storage, permissions, resource limits, or the reported underlying problem.
- After completion, verify the restored starting version before retesting.
Do not create competing work
While restore is incomplete, do not start another update test, refresh, or destructive manual database/file operation. Let the saved restore reach a verified end state first.
Preserve a known starting state
Resuming an Interrupted Laboratory Restore is useful only when the restore point and current laboratory belong to the same latest test operation. If you cannot prove that relationship, refresh the laboratory from current production and perform a new test rather than manually reconstructing a state and reusing old evidence.
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.