> 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/resultset-saved.md). # 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 | Setting | Required | Description | | --------- | -------- | ----------------------------------------------------------------------------------- | | 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 | 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/trigger/on-an-event/resultset-saved.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.