> For the complete documentation index, see [llms.txt](https://guides.transcript.study/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.transcript.study/transcript-extension/extension/troubleshooting.md).

# Troubleshooting

If you experience issues with the extension, try these quick fixes:

1. **Refresh the Page:**
   * Press **CTRL + R** on your keyboard to refresh the page.
2. **Check for Updates:**
   * Ensure you're using the latest version of the extension from the Chrome Web Store.
   * Make sure your browser itself is updated to the latest version, since outdated browsers can cause compatibility issues.
3. **Reinstall the Extension:**
   * If problems persist, remove the extension and reinstall it from the Chrome Web Store.

***

#### Common Error Messages

* **No Question Selected:** Make sure both the question and answer content are highlighted.
* **Extension Updated:** Refresh the page to continue.
* **Network Unavailable:** Check your internet connection and try again.
* **Server Unreachable:** Ensure your network isn't blocking connections to our servers.
* **Transcript Failed:** Retry your search. Contact support if the issue continues.
* **Unknown Error:** Retry your search. Contact support if the issue continues

***

{% hint style="info" %}
**Need More Help?**\
If you encounter any problems not covered here, please [contact us](https://transcript.study/support). We're here to ensure your experience is as smooth as possible!
{% endhint %}


---

# 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://guides.transcript.study/transcript-extension/extension/troubleshooting.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.