> For the complete documentation index, see [llms.txt](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/interactive-blocks/debugging-with-occurrences.md).

# Debugging with Occurrences

#### What is an occurrence? <a href="#what-is-an-occurrence" id="what-is-an-occurrence"></a>

An occurrence is a specific instance of a case captured during an audit. It's the exact element on a specific page where the issue was detected.

While cases show you the pattern (like `.product-price` on product pages), occurrences show you a single instance with the context you need to debug it.

#### Occurrence properties <a href="#occurrence-properties" id="occurrence-properties"></a>

Each occurrence on the case page shows:

* **Occurrence key**: identifier for this instance
* **Status**: Active, Resolved, or Regressed
* **URL**: the page where the occurrence was detected
* **Thumbnail**: element screenshot, or page screenshot when an element shot isn't available

Expand an occurrence to see:

* **Page and element screenshots**: visual evidence of the instance
* **Element selector**: the CSS selector for this exact element
* **HTML context**: the surrounding HTML, with the option to suggest a fix to the snippet
* **Last detected**: the most recent audit that found this occurrence

#### When to use occurrences <a href="#when-to-use-occurrences" id="when-to-use-occurrences"></a>

Occurrences are your debugging toolkit. Use them when you need to:

* **Debug edge cases**: when your fix didn't work as expected
* **Understand regressions**: why something reappeared after being resolved
* **Verify fixes**: confirm your change actually worked
* **Handle data issues**: when content is the problem, not code

For example, if you fixed the CSS for `.product-price` but still see 2 out of 10 occurrences remaining, open those specific occurrences to see what's different about them.

#### Statuses <a href="#statuses" id="statuses"></a>

An occurrence is in one of three states at any time:

* **Active**: found in the latest audit
* **Resolved**: previously found, not detected now
* **Regressed**: was resolved, now detected again

#### Next steps <a href="#next-steps" id="next-steps"></a>

Now that you understand what cases and occurrences are, the next section shows you when to work at each level.

* When to use cases vs occurrences: choose the right level for your fix


---

# 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.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/interactive-blocks/debugging-with-occurrences.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.