Clicking the gear icon in the scenario editor will open the Scenario settings panel allowing you to specify advanced settings for a scenario.
This option determines how Integromat should proceed if an error occurs during the execution of a scenario. With this option enabled, the scenario is paused and moved to Incomplete executions. This gives you the possibility to fix the issue and continue executing from where the scenario was stopped. If this option is disabled, the scenario run is stopped and a rollback is started.
This option determines how Integromat should proceed if an error occurs and the execution of a scenario is moved to the Incomplete executions. If the Sequential processing option is enabled, Integromat will stop processing the task sequence altogether until all incomplete executions are resolved. If the Sequential processing option is not enabled, the scenario will continue to run according to its schedule accompanied by attempts to repeat the incomplete executions.
Once a scenario has been executed, you can by default display information about which data were processed by modules in the scenario. If you do not want this information to be stored, enable the Data is confidential option.
If you enable the Data is confidential option, please be aware, that we have very limited possibilities to solve errors that may occur during the execution of a scenario.
Whether to enable data loss if Integromat fails to save a bundle to the queue of incomplete executions (e.g. due to a lack of free space). With this option enabled, the data will be lost in order to prevent scenario execution from being interrupted. This option is well suited for scenarios where the highest priority is continuous execution and the incoming erroneous data is not that important.
Besides, when executing a scenario, it can happen that one of the modules encounters a file that is larger than the maximum allowed size. In this case, Integromat proceeds in accordance with the setting of the Enable data loss option and a warning message will be shown.
The Autocommit settings applies to transactions and defines the way of processing a scenario. If the Autocommit option is on, the commit phase on each module starts immediately after completing the operation phase. With the Autocommit option disabled, no commit occurs until the operations are executed on all modules (default mode).
Defines the maximum number of cycles allowed during the execution of a scenario.