# Major Bugs, Outages, Feedback, Discord, Support, Releases

### Major Bugs and Outages:

* All Clear

### Discord

* Join our [Discord Server ](https://discord.gg/FgD9S2MCYB)to find community, hear updates, discuss use cases,

### Support

* Email <support@nimbalyst.com>

### In App Feedback

* Click the feedback icon
*

```
<figure><img src="../.gitbook/assets/image (19).png" alt=""><figcaption></figcaption></figure>
```

* Use the embedded skills to report a bug or request a feature

  <figure><img src="/files/9uulcc3o4xBnINzf2yA5" alt=""><figcaption></figcaption></figure>

### GitHub

Nimbalyst is open source. Browse the code, star the repos, or contribute at <https://github.com/nimbalyst>.

* Submit your feature requests and bug reports here: <https://github.com/Nimbalyst/nimbalyst/issues>
* Pull requests welcome — see the contributing guide in the main repo

### X and LinkedIn

* If you are loving Nimbalyst, please tweet about it and mention @nimbalyst. Follow us there too.
* X: <https://x.com/nimbalyst>
* LinkedIn: <https://www.linkedin.com/company/nimbalyst>
* YouTube: <https://www.youtube.com/@nimbalyst>

### Release Notes?

Please find our Release Notes [here](https://github.com/Nimbalyst/nimbalyst/releases)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nimbalyst.com/getting-started/feedback-discord-support-releases.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.