When to Download Reports Before Removing a Laboratory

Download any evidence you need before removing or refreshing a laboratory because those actions can delete the active private environment and temporary restore/rollback artifacts.

Download before destructive lifecycle actions

• The per-update report after laboratory testing.
• An updated report after production push/validation.
• The final report after any production rollback when used.
• Any screenshots/log excerpts needed for private support or your maintenance record.

Why timing matters

Removing the laboratory deletes associated temporary lab restore points and production rollback checkpoints. Refresh replaces the copied environment. Retained historical evidence can persist separately, but you should not rely on a destructive action preserving every temporary artifact you might later want.

Security after download

Reports can contain site paths, versions, URLs, change details, and production-derived evidence. Store them with the same care as other maintenance/security records.

Read evidence in context

Use When to Download Reports Before Removing a Laboratory together with the other evidence for the same tested item. A version check, route check, log message, screenshot, or file/database diff is strongest when it agrees with the surrounding evidence and your own reproduction in the private laboratory; no single signal should be treated as universal compatibility proof.

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.