Scenario settings panel
Clicking on the gear icon in the scenario editor will open the Scenario settings panel allowing you to set various advanced scenario settings:
Allow storing incomplete executions
This option determines how Integromat will 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 stops, and a rollback phase is started.
Sequential processing
This option determines how Integromat will 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 disabled, the scenario will continue to run according to its schedule, accompanied by repeated attempts to rerun the incomplete executions.
Data is confidential
Once a scenario has been executed, you can by default display information about which data was processed by modules in the scenario. If you do not want this information to be stored, enable the Data is confidential option.
Enable data loss
This option has to do with enabling 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 interruptions in the overall scenario execution. This option is well-suited for scenarios where the highest priority is continuous execution and the incoming erroneous data is not that important.
Beyond that, 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.
Auto commit
The Auto commit settings apply to transactions and define the way to process a scenario. If the Auto commit option is on, the commit phase on each module starts immediately after completing the operation phase. With the Auto commit option disabled, no commit occurs until operations are executed for all modules (this is the default mode).
Maximum number of cycles
Setting more cycles can be useful when you want to prevent connection interruption to a third-party service and assure that all records are processed within the one scenario run.
If the scenario starts with a polling trigger, the setting defines the maximum number of cycles allowed during the scenario execution.
If the scenario starts with an instant trigger, the setting is ignored and the actual value depends on the Process webhooks separately option:
- If the Process webhooks separately is disabled (default setting), the actual value is set to 100. All the pending webhooks (up to 100) are processed during a single scenario execution, one webhook per one cycle.
- If the Process webhooks separately is enabled, the actual value is set to one. Each pending webhook is then processed in a separate scenario execution (containing just one cycle).
If the scenario does not start with a trigger (instant/polling), the specified maximum number of cycles will always be performed.
Example
Dropbox > Watch files retrieve files added to a folder and the Google Sheets > Add a Row module inserts the file name and file size to a new row in the sheet.
A) Max number of cycles is set to 1 (default)
The Maximum number of returned files in the Dropbox > Watch files module is set to 10.
If 100 files are added to the Dropbox folder and the Maximum number of returned files field is set to 10 then 90 files will be left unprocessed after one scenario run. The next 10 files will be processed in the next scheduled scenario execution.
B) Max number of cycles is set to 10
The Maximum number of returned files in the Dropbox > Watch files module is set to 10.
If 100 files are added to the Dropbox folder and the Maximum number of returned files option is set to 10 then 10 files will be processed during the first cycle, the next 10 files in the second cycle, the next 10 files in the third cycle, and so on, until all files are processed.
All files are processed within the one scenario run.
You can see the already run cycles in the scenario run details:
Process webhooks separately
If this option is enabled, each pending webhook is processed in a separate scenario execution (containing just one cycle) rather than using multiple cycles inside a single execution. See the Maximum number of cycles for further details.
One of the interesting uses of this new setting is to work around the MAXIMUM EXECUTION TIMEOUT errors.
Number of consecutive errors
Defines the maximum number of consecutive execution attempts before the execution of a scenario is deactivated (excluding DataError, DuplicateDataError and ConnectionError).
