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

# Troubleshooting

If you are experiencing any issues with Smart Launcher, here you can find out how to proceed.

1. **Frequently Asked Questions (FAQ):**
   * You can find here a list of frequently asked questions and instructions on how to resolve common problems\
     [Smart Launcher 6](/products/faq.md)
2. **Reddit Community:**
   * Our Reddit community is a valuable resource for Smart Launcher users. You can find the community at [www.reddit.com/r/smartlauncher/](https://www.reddit.com/r/smartlauncher/). Feel free to share your feedback, ask questions, and seek assistance from other users who may have encountered similar issues.
3. **Contacting Support:**
   * If you have exhausted all other options and still need assistance, you can reach out to us via email at <support@smartlauncher.net>. Please keep in mind that we are a small team, and while we will do our best to respond, we may not be able to address every inquiry promptly.

Remember, we encourage you to utilize the FAQ and our Reddit community before contacting support. These resources are designed to help you find solutions quickly and efficiently.


---

# 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.smartlauncher.net/products/faq/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.