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
An agreed evaluation scope and confirmed integration version. Gateway, SDK, adapter, playground and binding screens are marked planned in the reviewed product navigation.
Steps
- Distinguish detector failure, policy rejection and enforcement failure. A permit decision without a verified enforcement record is not proof that protection completed.
- 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
Distinguish detector failure, policy rejection and enforcement failure. A permit decision without a verified enforcement record is not proof that protection completed.