> For the complete documentation index, see [llms.txt](https://docs.finops.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finops.softwareone.com/policies/quotas-and-budgets/view-policy-violation-history.md).

# View policy violation history

A violation history is available for those policies where the resource count or the expenses have exceeded the quota or budget. 

Violated policies are displayed in red on the **Quotas and budgets** page.

### View the policy violation history

To view the policy violation history:

1. Navigate to the **Quotas and budgets** page.
2. In the list of policies, find the policy for which you want to view the violation history.
3. Select the policy name.
4. On the policy details page, use the **Policy Violations History** section to view details including:
   1. The date and time when the policy violation occurred.
   2. The budgeted expense value vs the actual expense.
   3. The resources linked to the quota or budget.


---

# 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.finops.softwareone.com/policies/quotas-and-budgets/view-policy-violation-history.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.