> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/faqs/how-to-send-more-information-for-trouble-shooting-on-the-web.md).

# How to send more information for trouble shooting on the web

SharinPix can require to get access to a HAR (HTTP Archives) which records the requests and responses that your browser makes with the SharinPix Web Application.

In order to do so you have to:

1. Start the capture
2. Reproduce the behavior
3. End and save the capture
4. Send the file to Support for review

To start the capture, you can follow those steps under Chrome:

1. In Chrome, go to the page within SharinPix where you are experiencing trouble.
2. At the top-right of your browser window, click the Chrome menu (⋮).
3. Select **Tools > Developer Tools**. The Developer Tools window opens as a docked panel at the side or bottom of Chrome.
4. Click the **Network** tab.
5. Select **Preserve log**.
6. You will see a red circle at the top left of the Network tab. This means the capture has started. If the circle is black, click the **black circle** to start recording activity in your browser.
7. **Refresh the page** and reproduce the problem while the capture is running.
8. After you successfully reproduce the issue, right click on any row of the activity pane and select **Save as HAR with Content**.
9. Select the **Console** tab.
10. Right-click anywhere in the console and select **Save as...**.
11. Name the log file **Chrome-console.log**.
12. Send both files as shared links in a reply to your support request


---

# 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.sharinpix.com/faqs/how-to-send-more-information-for-trouble-shooting-on-the-web.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.