# Policy Evaluations
When a configured policy is not followed, the associated GitHub Actions workflow run will be blocked automatically. This helps enforce organization-wide security and compliance standards.
In such a case, you will see the following message within the workflow run:
```
The run was canceled by @stepsecurity-app[bot].
```
### Viewing Blocked Runs in the Dashboard
To investigate blocked runs, go to the “Policy Evaluations” dashboard under Run Policies in the StepSecurity platform.
This dashboard provides:
* A list of recent policy evaluation events across your organization.
* Information about the repository, workflow file, and timestamp of each event.
* The status of the run (e.g., Blocked).
* A direct link to the workflow run for deeper inspection.
### Understanding Why a Run Was Blocked
Click the arrow next to any listed evaluation to expand detailed information about:
* The specific policy or policies that were violated (e.g., *Do not allow GitHub-Hosted Runners*).
* The reason the run was blocked, based on the conditions defined in the policy (e.g., the job was configured to run on ubuntu-latest, which violates the organization’s policy against using GitHub-hosted runners)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.stepsecurity.io/github-actions/workflow-run-policies/policy-evaluations.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.