# Error Classification

In Zipy, everything revolves around errors. Once the session replays and errors on your web app are captured, Zipy maps and clubs multiple session replays with the same error into a single bucket. The dashboard showing all these error buckets in a tabular view is called the “Error Classification'' dashboard. 

As of today, errors are classified into two categories: Frontend and Network errors. Read more about the errors supported [*here*](https://docs.zipy.ai/faqs/what-kind-of-errors-can-be-tracked-with-zipy).

In Zipy’s Error Classification screen, your developers can see all the errors displayed by their type, description, count, no. of sessions where the error has been captured, latest occurrence timestamp, OS, and browsers where the error has occurred. Clicking any row would take you to the error context screen, which gives you access to all the session replays where the respective error has occurred along with the user behavior and user environment details for the same, thus helping you debug better.

Following is a screenshot of “Error Classification” dashboard in Zipy: 

<figure><img src="/files/Azepv5HHVU9qSw7D54Fq" alt=""><figcaption></figcaption></figure>

<br>


---

# 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.zipy.ai/faqs/error-classification.md?ask=<question>
```

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.