> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/trigger/on-an-event/dataflow-failed.md).

# Dataflow failed

**Category:** Trigger

**Version:** 1.0

**Last updated:** January 28, 2026

**Author:** Any2Info

***

### When is the trigger raised

The trigger is raised when the configured **error count threshold** is reached within the specified **time window** for the selected dataflows.

The trigger **does not fire on every failure**, only when the threshold condition is met.

***

### What counts as a failed dataflow

A dataflow is considered **failed** when **one or more nodes throw an exception**, regardless of whether the error is handled later in the flow.

Handling failed rows or exceptions inside the dataflow **does not prevent** the dataflow from being marked as failed for the purpose of this trigger.

***

### Configuration options

#### Dataflows

Defines the dataflows this trigger should respond to.

* One or more dataflows can be selected
* If **no dataflow is selected**, the trigger will **never be raised**

***

### Specific settings

#### Error count

Defines how many times a dataflow must fail before the trigger is raised.

#### Time window

Specifies the time period in which the error count must be reached.\
If the threshold is not met within this window, the behavior depends on the selected window mode.

#### Window mode

Determines how failures are counted within the time window.

**Fixed**

* Counting starts when the **first error occurs**
* All failures are counted until the **time window expires**
* As soon as the error count threshold is reached, the trigger is raised
* After firing, a **new time window starts**

**Rolling**

* On each failure, the system checks how many failures occurred in the **past time window**
* If the number of failures in that window exceeds the threshold, the trigger is raised
* If another failure occurs later and the number of failures in the past window is still above the threshold, the trigger is raised **again**
* Unlike fixed mode, the count does **not reset automatically**

Both window modes respect the configured cooldown.

#### Cooldown

Specifies a period after the trigger fires during which it **cannot be triggered again**.

This is useful to prevent repeated executions when a dataflow keeps failing continuously.

***

### Usage

This trigger is typically used to:

* Notify administrators of failing dataflows
* Start reporting or alerting dataflows
* Trigger recovery or cleanup processes

***

### Tips & Best Practices

* In complex environments, it is recommended to have at least one dataflow with a **DataFlow Failed trigger** to ensure administrators are notified when issues occur.
* Use **error count** and **cooldown** together to prevent alert fatigue when a dataflow fails repeatedly.
* Prefer **rolling window mode** when detecting recurring instability, and **fixed window mode** when monitoring bursts of failures.

***

### Changelog

| Version | Date             | Change                               |
| ------- | ---------------- | ------------------------------------ |
| 1.0     | January 28, 2026 | Initial documentation version added. |


---

# 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 dynamically by asking a question.

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

```
GET https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/trigger/on-an-event/dataflow-failed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.