Scenario settings

you can access the {{scenario singular lowercase}} settings panel by clicking the gear icon in the {{scenario singular lowercase}} editor here you can set various advanced settings sequential processing you can allow {{product name}} to store information about incomplete {{product name}} executions the sequential processing setting determines how {{product name}} processes recurring incomplete executions the incomplete executions docid 6zznn7v35herrcjfccp9q folder must contain {{product name}} data if enabled, {{product name}} stops executing the {{scenario singular lowercase}} until you resolve all incomplete executions this option guarantees that {{product name}} will always solve incomplete executions in sequential order if disabled, the {{scenario singular lowercase}} continues to run according to its schedule a scenario docid\ scpfttwgfapf077ujo1jh , regardless of errors sequential processing also applies to webhooks docid 1yhunj8jvzyxip9cf3ps1 by default, {{product name}} processes webhooks in parallel when you enable sequential processing, {{product name}} waits until the previous execution is complete before starting the next one data is confidential after a {{scenario singular lowercase}} executes, you can scenario execution flow docid\ ydlsupyiberg8vmk99o2h about data processed by the modules this happens by default if you do not want to store this information, enable this setting if enabled, there are very limited options to solve errors that occur in a {{scenario singular lowercase}} execution allow storing of incomplete executions this setting determines what happens if a {{scenario singular lowercase}} run encounters an incomplete executions docid 6zznn7v35herrcjfccp9q you can choose how {{product name}} will process the data if enabled, the {{scenario singular lowercase}} is paused and moved to the incomplete executions docid 6zznn7v35herrcjfccp9q folder this gives you the possibility to fix the issue and continue from where the {{scenario singular lowercase}} stopped if disabled, the {{scenario singular lowercase}} run stops and starts a scenario execution, cycles, and phases docid\ m3kmlkl8455cs zz13ytb phase you can resolve each incomplete execution either manually or automatically the data in this folder counts towards the storage limits of your subscription plan enable data loss {{product name}} may fail to save a data bundle to the queue of incomplete executions docid 6zznn7v35herrcjfccp9q (e g due to a lack of free space) with this setting enabled, {{product name}} does not save the lost data this is to prevent interruptions in the make execution this option is well suited for {{scenario plural lowercase}} where continuous execution is the highest priority the incoming data is less important modules can encounter files larger than the working with files docid\ oauioo6oujv0fyglzmrte in this case, {{product name}} proceeds according to the enable data loss setting and displays a warning message the maximum file size depends on your subscription plan auto commit this setting applies to scenario execution, cycles, and phases docid\ m3kmlkl8455cs zz13ytb and defines the way to process a {{scenario singular lowercase}} this setting is enabled by default if enabled, the scenario execution, cycles, and phases docid\ m3kmlkl8455cs zz13ytb phase on each module starts immediately after the operation phase data is committed right away and cannot be restored in the case of an error if disabled, no commit occurs until operations are executed for all modules not every module supports transactionality only modules marked with the tag 'acid' support transactions commit trigger last this setting defines the module scenario execution, cycles, and phases docid\ m3kmlkl8455cs zz13ytb order after a successful {{scenario singular lowercase}} operation phase this setting is enabled by default if enabled, the commit phase skips the trigger and processes that module last if disabled, the commit phase occurs in the default order max number of cycles this setting defines the maximum number of cycles allowed during a {{scenario singular lowercase}} execution setting more scenario execution, cycles, and phases docid\ m3kmlkl8455cs zz13ytb can be useful when you want to prevent connection interruption to third party services this can also ensure all records are processed within the {{scenario singular lowercase}} run if you execute the {{scenario singular lowercase}} manually by clicking the run once button, the setting is ignored and only one cycle will be performed number of consecutive errors this setting defines the maximum number of consecutive execution attempts before the {{scenario singular lowercase}} deactivates (though there are exceptions listed in the overview of error handling docid 7 hehdtuu2xyys8 qurub if a {{scenario singular lowercase}} starts with an instant trigger, the setting is ignored and the {{scenario singular lowercase}} is deactivated immediately once the first error has occurred