# Errors
Error is a powerful way to view all your errors combined across users. There are two primary categories of errors that are captured by Zipy :
1. Frontend Errors
2. API Errors
By default the errors are sorted by latest error first. You can sort the errors by total sessions, count of all errors, OS, browser and time when it occurred.
Clicking on a given error will playback the latest session where the error occurred. The Zipy Error Session Player will show the following data
1. The complete session playback
2. Exact point on timeline where the error occurred
3. Breadcrumbs will also show the exact error detail
4. Dev Tools will contain the error information details. This could be stack trace, console errors, API errors and exception captured via Zipy logs.
5. User environment details
6. All user session where the given error was detected
The following actions can be taken inside an error session screen
1. Share the session URL with your team members with exact timestamp
2. Create a JIRA ticket with auto filled details
3. Link a JIRA ticket with auto filled details
---
# 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/product-features/errors.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.