> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/dashboards/policies/check-result.md).

# Check Result

The check result pop-up appears when you click on a check result from the policy viewer. This shows you the details of a check result and what triggered it. The following information is available:

* **Check type.** The check that was used. For more details click the help icon to open the online documentation.
* **Severity.** The severity level of the check result. Possible values are Low, Medium and High.
* **Category.** The check type category. Possible values are Security, Maintainability, Quality, and Standards.
* **Message.** An optional message generated by the check. This provides extra information to help you fix the issue found by the check.
* **Target.** The best practice target value configured for this check. This is taken from the check configuration.
* **Value.** The actual value found by the check.
* **Element type.** The type of model / app element that was checked.
* **Element name.** The name of the model / app element that was checked. Note: Some element types do not have a name (E.g. the 'app' element).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bluestorm.io/dashboards/policies/check-result.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.