Responding to a Laboratory Update That Needs Attention

A laboratory update that “needs attention” has evidence or an operation condition that QCUL cannot honestly present as a clean production candidate.

Start with focused evidence

1. Expand the tested update row.
2. Open View Problems or the issue report when available.
3. Review package/version, route, browser, log, and file/database evidence relevant to the problem.
4. Open the laboratory and reproduce the affected workflow manually.

Choose the right next action

• Use Undo Lab Update when the latest valid restore point can return the lab to the starting state.
• Correct the extension/site/update-source problem and retest.
• Refresh the laboratory when the clone itself has become stale/uncertain.
• Stop the production plan if the problem is unexplained.

Do not normalize warnings away

A warning can be acceptable after informed review, but it must be understood. The human review confirmation is not a “make green” switch for unresolved technical evidence.

Preserve a known starting state

Responding to a Laboratory Update That Needs Attention 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.