> 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/workflows/how-to-notify-report-owners-when-a-refresh-fails.md).

# How To: Notify report owners when a refresh fails

## **Use case: Routing a failed refresh alert to the right owner without leaving Datalogz**

This use case explains how to create a [workflow](/guides/workflows.md) that lets a BI admin notify a report owner directly from a failed refresh alert, without switching to email, looking up contact details, or writing a message from scratch.

### **Why is it important?**

When a report fails its scheduled data refresh, business users may be consuming stale or incomplete data without knowing it. The faster the owner is informed, the faster the issue gets investigated and resolved. Without a workflow, notification is manual: find the alert, identify the owner, open email, write the message, send it. Across dozens of alerts a week, this adds up, and follow-through is inconsistent.

A workflow eliminates that overhead. It surfaces a single button on every matching alert, and logs the action so nothing falls through the cracks.

### **Who is responsible for it?**

This use case is typically owned by:

* BI administrators
* Analytics platform owners
* BI Ops or Center of Excellence (CoE) teams

These roles are responsible for monitoring BI health, resolving operational issues, and ensuring report owners are held accountable for the assets they manage.

### **Steps**

1. In Datalogz Control Tower, go to **Settings > Workflows > Definitions**.
2. Click **Create Workflow**.
3. Enter a name and description, for example: *Notify report owner: failed refresh*. This is what users will see on the alert page.
4. Under **Trigger Configuration**, select **Manual**.
5. Set the **Connector** to one of your BI connectors, or leave blank to apply across all connectors.
6. Under **Linked** **Monitors**, select the **Failed Refresh** monitor to restrict the workflow to that alert type only.
7. Under **Plugin**, select **Send Email**.
8. Click **Save**. The workflow is now live and will appear on every failed refresh alert that matches the connector filter.

### **Running the workflow from an alert**

When a failed refresh alert fires:

1. Open the alert in Datalogz Control Tower.
2. Click the **Run Workflow** button and select **Notify report owner: failed refresh**.
3. In the dialog, set the **Recipient type** to **User** and select the report owner.
4. Write a comment.
5. Click **Run**.

Datalogz Control Tower sends the email immediately. The session is recorded in the workflow [history view](/guides/workflows/viewing-workflow-history.md), including the recipient, timestamp, and outcome.


---

# 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/workflows/how-to-notify-report-owners-when-a-refresh-fails.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.