When Push to Production Becomes Available

Push to Production becomes available only after QCUL has a completed laboratory test that is eligible for production review and the required human/protection conditions can be satisfied.

Required path to the push

1. Complete the selected update test in the private laboratory.
2. Investigate any warning/problem that prevents a production-ready result.
3. Open the updated lab and complete human review.
4. Record I reviewed this update in the laboratory.
5. Choose one production protection option.
6. Use Check Production Now when you need a fresh readiness evaluation.

The button is not the only gate

When Push to Production is submitted, QCUL reloads the tested item and runs server-side readiness checks again. A stale visible button cannot bypass a changed starting version, missing package/hash, wrong site identity, permission failure, conflicting operation, or invalid recovery choice.

If push is unavailable

Read the tested row/status and resolve the specific missing condition. Do not recreate a laboratory approval by editing database state or form values.

Production change rule

For When Push to Production Becomes Available, 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.