You can allow Axelor Connect to store information about incomplete scenario executions.

The sequential processing setting determines how Axelor Connect processes recurring incomplete scenario executions. The Incomplete executions folder must contain scenario data.

	Note
	Sequential processing also applies to webhooks. By default, Axelor Connect processes webhooks in parallel. When you enable sequential processing, Axelor Connect waits until the previous execution is complete before starting the next one. See webhooks for more information.

After a scenario executes, you can display information about data processed by the modules. This happens by default.

If you do not want to store this information, enable the data is confidential setting.

	Caution
	If enabled, there are very limited options to solve errors that occur in a scenario execution.

This setting determines what happens if a scenario run encounters an error. You can choose how Axelor Connect will process the data.

You can resolve each incomplete execution either manually or automatically.

	Note

Axelor Connect may fail to save a data bundle to the queue of incomplete executions (e.g. due to a lack of free space). With this setting enabled, Axelor Connect does not save the lost data. This is to prevent interruptions in the scenario execution.Bundle

This option is well-suited for scenarios where continuous execution is the highest priority. The incoming data is less important.

Scenario modules can encounter files larger than the maximum allowed size. In this case, Axelor Connect proceeds according to the enable data loss setting and displays a warning message.

	Note

This setting applies to transactions and defines the way to process a scenario. This setting is enabled by default.

	Note
	Not every module supports transactionality. Only modules marked with the tag 'ACID' support transactions.

This setting defines the module commit order after a successful scenario operation phase. This setting is enabled by default.

This setting defines the maximum number of cycles allowed during a scenario execution.

Setting more cycles 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 run.

If you execute the scenario manually by clicking the Run once button, the setting is ignored and only one cycle will 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.

1. Max number of cycles is set to 1 (default)

   

   The Limit field in the Dropbox > Watch files module is set to 10.

   

   If 100 files are added to the Dropbox folder and the Limit 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.

2. Max number of cycles is set to 10

   

   As before, the Limit field in the Dropbox > Watch files module is set to 10.

   If 100 files are added to the Dropbox folder and the Limit field 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.

This setting defines the maximum number of consecutive execution attempts before the scenario deactivates (excluding DataError, DuplicateDataError and ConnectionError).

	Note
	If a scenario starts with an instant trigger, the setting is ignored and the scenario is deactivated immediately once the first error has occurred.