> For the complete documentation index, see [llms.txt](https://help.refractbot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.refractbot.com/online-dashboard/announcements.md).
# Announcements
The **Announcements** tab is where the team posts important updates: module changes during drops, known issues, and service status.
Open it here: [dashboard.refractbot.com/announcements](https://dashboard.refractbot.com/announcements)
Announcements are tagged by severity. CRITICAL posts usually mean act now.
## Where announcements show up
Announcements appear in two places: here on the dashboard, and as a pop-up inside the bot itself. That is deliberate. Discord servers can go down or get deleted, and it has happened to ours before. Announcements are the channel that always works, so important updates reach you even if Discord does not.
Each announcement is tagged by severity. **CRITICAL** means read it now, it usually involves an update or issue during an active drop. **INFO** is general news. Click **Refresh** to pull the latest.
{% hint style="info" %}
**Something acting strange during a drop?** Check Announcements first. If a site starts throwing new blocks or errors, chances are there is already a post about it, sometimes with an update to restart into.
{% endhint %}
---
# 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.refractbot.com/online-dashboard/announcements.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.
