Scenario Settings

You have the option to permit the platform to store information regarding incomplete scenario executions.

The sequential processing setting determines how inMultifamily processes incomplete scenario executions that occur on a recurring basis. To make use of this feature, the Incomplete executions folder must contain scenario data.

If you enable this setting, inMultifamily will halt scenario execution until you have resolved all incomplete executions. This option ensures that inMultifamily will address incomplete executions in a sequential order.

If you disable this feature, the scenario will continue to run according to its pre-defined schedule, regardless of any errors encountered.

Note:

Sequential processing also applies to webhooks. By default, inMultifamily will process webhooks in parallel. However, if you enable sequential processing, inMultifamily will wait until the previous webhook execution is complete before initiation the next one. 

For additional information on webhooks, please refer to the relevant resource on the topic.

In inMultifamily, after a scenario is executed, information regarding data processed by the modules is automatically displayed.

If you do not wish to retain this data, you can enable the "data is confidential" setting. This feature ensures that any sensitive data processed during the scenario execution is not stored by the platform.

CAUTION:


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

The error handling setting governs how data is processed when a scenario execution encounters an error. You have the ability to choose how inMultifamily handles this data.

If you enable this setting, the scenario will be paused and moved to the "Incomplete executions" folder. This provides you with the opportunity to resolve the error and continue executing the scenario from where it stopped.

If you disable this setting, the scenario execution will stop and a rollback phase will begin.

In order to resolve each incomplete execution, you have the option to either manually address the issue or automate the process.

Note:

The data in this folder counts towards the storage limits of your subscription plan.

Inside inMultifamily, there is a setting that governs how data bundles are handled if a failure occurs while attempting to save them to the queue of incomplete executions.

If this setting is enabled, inMultifamily will not save any data bundles that have been lost (for example, due to a lack of free space). This is done to prevent any disruptions to the scenario execution process.

This option is particularly suitable for scenarios where continuous execution is of utmost importance, and incoming data is of lesser significance.

If a scenario module encounters a file larger than the maximum allowable size, inMultifamily will follow the enable data loss setting and present a warning message to the user.

Note:

The maximum file size depends on your subscription plan.

In inMultifamily, there is a setting that pertains to transactions and determines how a scenario should be processed. This setting is enabled by default.

If this setting is enabled, the commit phase for each module will commence immediately after the operation phase. This means that data will be committed without delay and cannot be restored in the event of an error.

If this setting is disabled, no commit will occur until operations have been executed for all modules in the scenario.

Note:

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

In inMultifamily, there is a setting that determines the module commit order following a successful operation phase in a scenario. This setting is enabled by default.

If this setting is enabled, the commit phase will skip over the trigger and process that module last.

If this setting is disabled, the commit phase will follow the default order.

In inMultifamily, there is a setting that specifies the maximum number of cycles permitted during a scenario execution.

Increasing the number of cycles can be beneficial in situations where it is essential to avoid connection interruptions to third-party services, or when it is crucial to ensure that all records are processed within a single scenario execution.

If you manually execute the scenario using the "Run once" button, the setting will be 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.

In inMultifamily, there is a setting that determines the maximum number of consecutive execution attempts that can occur before a scenario becomes deactivated (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 occured.