> For the complete documentation index, see [llms.txt](https://help.clausebuddy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clausebuddy.com/encountering-problems.md).
# Encountering problems?
## Close & reopen
The first thing you should try, is to close the ClauseBuddy panel and reopen it. Usually, any issue you encounter will be resolved by this. This effectively "reboots" the software — which, as usual, solves half of the technology problems you can ever run into.
## Clause title or body issues
Microsoft Word sometimes performs weird stuff when copying text from its document (left side) to the ClauseBuddy boxes (right side). If the text is behaving strangely, then try to remove all text formatting by selecting all text and pressing the **eraser icon**.
## Hard reset
When closing and reopening does not work, you can try to reset ClauseBuddy.
Don't worry: this merely removes your locally stored settings, i.e. the configuration stored in your copy of Microsoft Word (or Outlook). Although you will have to login again using your security code(s), this will not affect any clauses that you have stored on the server.
In Windows, you have to [remove a specific folder containing all plugin information](https://docs.microsoft.com/en-us/office/dev/add-ins/testing/clear-cache).
If you are using a Mac, click on the **"i**" icon in the top right corner, choose *Clear Web Cache*, and close & reopen ClauseBuddy.
## If all else fails...
[Send us an email](mailto:hello@clausebuddy.com) and describe where you get stuck. We'll then try to un-stuck you.
---
# 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://help.clausebuddy.com/encountering-problems.md?ask=&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.
