Why Undo Lab Update Never Changes Production

Undo Lab Update is intentionally confined to the private copied directory/database prefix; it never rolls back the live production Joomla site.

Isolation boundary

The laboratory configuration points to a run-specific database-table prefix and copied filesystem root. Its restore point is created from those lab objects before the test. Production is not the checkpoint target.

Different production feature

If you later push the tested update to production and selected a temporary QCUL production checkpoint beforehand, the separate Undo Production Push workflow can restore the protected live scope during its validity window. That is a different checkpoint, operation, and authorization boundary.

Safe practice

Always confirm the page/banner says you are reviewing the private lab before experimenting. Perform push/production undo only from the live QCUL installation, which requires stricter permissions/Super User checks.

Preserve a known starting state

Why Undo Lab Update Never Changes Production 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.