Resultset saved
Category: Trigger
Version: 1.0
Last updated: January 28, 2026
Author: Any2Info
Description
The Resultset Saved trigger starts a dataflow automatically whenever a selected resultset is saved.
Unlike the Resultset Changed trigger, this trigger does not check whether the data has changed. It is raised every time the resultset is saved, even if the stored data is identical to the previous version.
How it works
The trigger is linked to a single resultset
A resultset is saved by another dataflow using the Save Resultset node
Every save action raises this trigger
No comparison or change detection is performed
This makes the trigger suitable for workflows that must react to every save event.
Configuration Options
Resultset
Yes
The resultset to monitor. The trigger is raised every time this resultset is saved.
Usage
Use the Resultset Saved trigger when a dataflow should always react to a save action, regardless of whether the data has changed.
Typical use cases include:
Chaining dataflows where every save should trigger follow-up processing
Auditing or logging save events
Forcing recalculation or redistribution of data
Driving downstream processes that depend on save actions rather than data changes
Notes & Behavior
The trigger is executed every time the resultset is saved
Identical data still triggers execution
A dataflow can contain only one trigger
Tips & Best Practices
Use this trigger when change detection is not required
Prefer Resultset Changed if unnecessary executions should be avoided
Do not use the Save Resultset node in the same dataflow as this trigger, as this can cause an execution loop
Changelog
1.0
January 28, 2026
Initial documentation version added.
Last updated
Was this helpful?