Evaluation guide
Troubleshoot a run
Isolate the failure and prepare a useful, redacted support request.
Confirm the enabled version and permissions in your environment. These guides do not announce a general release.
Before you start
A bounded evaluation scenario and a person authorised to approve it. No production execution or automatic approval is assumed.
Steps
- If the target, approved revision or verification evidence is missing, stop the evaluation at that boundary. Record the gap rather than inferring permission.
- Compare the observed outcome with the expected result. Keep the relevant identifier and a redacted record so a colleague can review the same case.
- Provide the timestamp, product/environment version, expected and observed result, and a redacted request or run identifier. Remove credentials and personal data.
Check the result
Compare the observed outcome with the expected result. Keep the relevant identifier and a redacted record so a colleague can review the same case.
If it does not work
If the target, approved revision or verification evidence is missing, stop the evaluation at that boundary. Record the gap rather than inferring permission.