> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/writebackextreme/troubleshooting-and-faq/extension-errors/how-to-debug-the-extension-in-general.md).

# How to debug the extension in general

When the extension shows unexpected results, the best starting point is to inspect the debug tools in the browser to find out if there is an error or maybe an unexpected result in the network. This only works in the browser so it is necessary to publish the dashboard first.

1. In chrome press `Control + Shift + J`(or click on the 3 vertical dots in the top right corner of the browser and select More tools->Developer tools)
2. Reload the page to make sure developer tools is recording properly&#x20;
3. First look at the console tab to see if there are any error messages (generally displayed in red). Tableau also generates messages/warnings so sometimes it seems a bit cluttered.
4. The next interesting page is the network tab. This displays all network traffic that is generated by the dashboard. To get a good overview of the communication of WriteBackExtreme, filter on the requests on Fetch/XHR and put your WriteBackExtreme domain into the search box:

   &#x20;![](/files/mZ2jaSVT4a4lYiQHC8BX)

   If there is any error in the communication you will see it there.
5. When you cannot find any problems as described above you can also download the information by clicking the download icon (last icon in the screenshot above) And send us the result. Then we can start an investigation on it.


---

# 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.infotopics.com/writebackextreme/troubleshooting-and-faq/extension-errors/how-to-debug-the-extension-in-general.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.
