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

# Troubleshooting

This page is continually updated with commonly asked questions that the FieldDoc team receives. If you can't find your answer here, please [Get in Touch](/support/get-in-touch.md).\\

## Creating an Account

<details>

<summary>The 'Create Account' button is unresponsive</summary>

During the registration process, some users have reached out because the "create account" button on the registration page is unresponsive. In other words, they fill out the registration form but when they click the Create account button, nothing happens. Here are some tips to try if this happens to you:

1. Clear your browser cache and reload the webpage.
2. Make sure that your browser is up to date with any system updates.
3. Check with your IT department to make sure that FieldDoc.org is added to their safe list.

</details>


---

# 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.fielddoc.org/support/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.