What Happens When the Production Rollback Window Expires

When the configured production rollback window expires, QCUL no longer offers Undo Production Push and the temporary checkpoint becomes cleanup data rather than an active recovery option.

What expiry means

• The checkpoint’s rollback eligibility ends.
• Scheduled/operational cleanup removes expired private checkpoint data.
• The tested update/report remains as evidence, but the quick QCUL undo path is gone.

What expiry does not do

It does not undo the update automatically. A successful production update remains installed. If a problem is found after expiry, use your independent backup/recovery method or an appropriate vendor/Joomla remediation plan.

Choose a realistic window

For future pushes, configure enough time to perform the real live review. Do not choose 10 minutes if your acceptance process routinely takes an hour.

Recovery discipline

When working with What Happens When the Production Rollback Window Expires, keep the independent backup available even if the QCUL checkpoint is valid. The checkpoint is a fast, short-lived update rollback mechanism; if its protected scope, validity window, or verification cannot satisfy the incident, move to the broader recovery plan rather than extending QCUL beyond its promise.

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.