Using Check Production Now

Check Production Now re-evaluates whether the exact tested update is still safe to offer for the current live site before you commit to a push.

Step-by-step procedure

1. Open the tested update row after laboratory review.
2. Select Check Production Now.
3. Read the production-safety result and any blocked reason.
4. If the selected update’s expected starting version, exact package, permissions, production identity, worker state, or protection choice is not valid, correct that condition.
5. Recheck before pushing if production changed while you were reviewing the lab.

Use it after meaningful delay/change

Run it when production changed during review, when the tested row was left open for a while, or after resolving a prior blocked condition. It refreshes safety evidence; it does not install the update.

What it does not change

The check does not alter the laboratory, download a replacement package, create a rollback checkpoint, or install anything. It only refreshes the current production-readiness comparison for the already tested item, so a blocked result should be fixed at its stated cause rather than bypassed.

Production change rule

For Using Check Production Now, the live site should change only through the explicit tested-item production workflow after current readiness checks pass. Do not substitute a new package, skip the review/protection decision, or run a second production action while QCUL already owns an active push/rollback state.

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.