> 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.&#x20;

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

### Viewing 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.finops.softwareone.com/policies/quotas-and-budgets/view-policy-violation-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
