Results
📖 Description
Saver actions are responsible for generating the final result of script execution.
The result includes data accumulated in the Script, Flow, and Page stores.
To extract and persist this data — for example, to a file or over the network — special saver actions are used.
They let you define which stores to include and can optionally attach the execution log.
Saver actions do not affect the flow execution itself, but allow capturing its state at any point.
🧩 Structure
| Field | Type | Required | Description | Default value |
|---|---|---|---|---|
storeTypes |
EngineStoreType[] | List of stores to include in the result (e.g., Script, Flow, Page). | ||
includeActionsLog |
bool | If true, includes the action execution log in the result. | false |
📋 Example
{
"action": "SaveToFile",
"storeTypes": ["Page", "Script"],
"includeActionsLog": true,
"path": "results/last-run.json"
}
Execution Logic
Saver actions use the BuildReport method to generate the result object.
It captures the current timestamp along with the target's URL and name, extracts data from the selected stores (Script, Flow, Page), and optionally includes the full execution log.
It also determines the overall flow status based on the outcome of each action — whether it succeeded, failed, or was skipped.