# Resultset changed

**Category:** Trigger

**Version:** 1.0

**Last updated:** January 28, 2026

**Author:** Any2Info

***

### Description

The **Resultset Changed trigger** starts a dataflow automatically when the content of a selected resultset changes.

The trigger monitors a specific resultset and is raised only when the stored data differs from its previous state. If no data has changed, the trigger will not execute.

***

### How it works

* The trigger is linked to a single **resultset**
* A resultset can be updated by another dataflow using the **Save Resultset** node
* When the stored resultset data changes, this trigger is raised
* If the resultset is saved again **without any data changes**, the trigger is **not** executed

This ensures the dataflow only runs when meaningful changes occur.

***

### Configuration Options

| Setting   | Required | Description                                                                                                 |
| --------- | -------- | ----------------------------------------------------------------------------------------------------------- |
| Resultset | Yes      | The resultset to monitor for changes. The trigger is raised when the content of this resultset is modified. |

***

### Usage

Use the **Resultset Changed trigger** when a dataflow should react to changes produced by another dataflow.

Typical use cases include:

* Reacting to updated or refreshed data
* Triggering follow-up processing after data preparation
* Synchronizing dependent dataflows
* Preventing unnecessary executions when data remains unchanged

***

### Notes & Behavior

* The trigger is only executed if **any of the containing data** in the resultset has changed
* Changes are detected on data level; saving an identical resultset does not trigger execution
* A dataflow can contain **only one trigger**

***

### Tips & Best Practices

* Use clear naming for resultsets to make dependencies between dataflows easy to understand
* Combine this trigger with focused downstream logic to process only what is necessary
* Use it to decouple dataflows while still reacting to changes reliably
* **Do not use the *****Save Resultset***** node in the same dataflow as this trigger**, as this can cause an execution loop

***

### Changelog

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