> For the complete documentation index, see [llms.txt](https://docs.browsee.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.browsee.io/understand-your-users/session-search/automatic-session-tags/frustration-click.md).

# Frustration Clicks or Rage Clicks

Frustration clicks are triggered when a user repeatedly clicks on the same are of the page.

Here is an example, let's say the burger menu on your mobile site breaks witha  new release. You will soon start noticing frustration clicks on it in Browsee, indicating that the element is not responding when user's click on it.&#x20;

![Frustration or Rage Click](/files/-LskaLDyf_ip_v3vblw8)

Most frustration clicks are signs of broken functionality, incomplete or errenous JS errors or network errors.

However, there are times when frustration clicks are triggered on UI elements like image sliders. In these case you can, go to the **User Experience** tab  and **Mark As Resolved** and Browsee will remember to not trigger a frustration click on that element.


---

# 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.browsee.io/understand-your-users/session-search/automatic-session-tags/frustration-click.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.
