> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/support/having-trouble.md).

# Having trouble?

### What to do if something is not working?

If you are facing an issue where a feature or function in your app is not working, the best way to resolve it is to contact our support team. Follow these steps to reach out support team when you face an error in your app:

**Step 1: Go to the support form**

* Visit the support form page here: [Submit a request](https://app.appmysite.com/email-support)

**Step 2: Share details of the issue**

* Clearly describe the issue you are encountering.
* Include your app details, screenshots, and any error messages if available.

**Step 3: Submit the form**

* Once you submit the form, our support team will review your request and get back to 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://docs.appmysite.com/support/having-trouble.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.