> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/alerts/alert-workflows.md).
# Alert Workflows
Alert workflows provide scripts directly within the Datalogz [Alert details](/guides/alerts/alert-details.md) page to help you resolve issues quickly and efficiently. These pre-configured scripts allow you to take immediate action on a problem.
## How to use alert workflows
To get started with an alert workflow, you'll first need to access the specific alert you want to work on and do the following:
1. Select an action on the Alert details page.
1. Click **Copy** or **Run** to use the script or click **Download Full Script**.
2. Execute the script: Run the provided script in your BI environment.
3. Validate that the action has been taken in the BI environment.
4. Once confirmed, update the alert's status.
### Add a comment when you change an alert's status
When you change an alert's workflow status, you can add a comment explaining the decision. The comment is saved with the alert and the most recent one appears on the Alert Details tab, so anyone reviewing the alert later can see who changed what and why.
1. On the Alert Details page, change the alert's **status** (for example from To Do to Resolved).
2. Enter a **comment** in the confirmation dialog describing what you did or why.
3. Click **Save**.
{% hint style="info" %}
A comment is optional, but a short note such as "Republished the dataset, refresh now succeeds" gives your team an audit trail and prevents duplicate work.
{% endhint %}
### Automatic status changes
To keep the alert queue focused on what is still live, Datalogz closes stale event-based alerts automatically. An EVENT alert with no new activity for 30 days is moved to **Potentially Resolved**. If the condition recurs, a new alert is raised, so nothing is lost. This keeps owners focused on active issues without manually clearing alerts that have quietly resolved themselves.
---
# 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.datalogz.io/guides/alerts/alert-workflows.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.
