> 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/administration/pipelines/check-policy.md).

# Check Policy

A check policy task will check the policies applicable to the target app and environment for compliance. The following options are available:

* **Proceed on Failure.** If enabled, the pipeline will continue executing when this step fails.
* **What is the minimum policy status required for this check to pass?** If the policy state returned by the policy check is the same or better than the selected status, the policy check task will pass. E.g. If you select 'warning' and the policy check returns the status 'warning', the policy check task will pass.

{% hint style="info" %}
If the revision for the current release has already been checked previosuly by the system (E.g. someone has manually checked the revision, or it was already deployed to a different environment), the stored result of the check will be used. 

However, if the revision has not yet been checked, the model for the revision will be processed and checked during the pipeline execution. This will incur delay during your pipeline execution as revision checks can take a long time to execute.

Additionally, if the settings of the policy that is applicable to your app have changed since the last time the revision was checked, it will be checked again by this task.
{% endhint %}


---

# 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/administration/pipelines/check-policy.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.