The scenario settings panel in Adobe Workfront Fusion

Access requirements

You must have the following access to use the functionality in this article:

To find out what plan, license type, or access you have, contact your Workfront administrator.

For information on Adobe Workfront Fusion licenses, see Adobe Workfront Fusion licenses.

Open the scenario settings

Allow storing incomplete executions

This option determines how Adobe Workfront Fusion proceeds if an error occurs during the execution of a scenario. With this option enabled, the scenario is paused and moved to View and resolve incomplete executions in Adobe Workfront Fusion. 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 forces all executions to happen in order, and is primarily relevant for Webhooks and for Incomplete Executions.

When sequential processing is enabled, parallel executions of the scenario are disabled.

Instant Webhooks

If a webhook trigger is configured as instant and “Sequential processing” is enabled, then all instant webhook payloads will be queued and processed in the order that they arrive. This can be useful when processing events from external systems in an exact order.

Incomplete Executions

If “Incomplete Executions” is also enabled, if an error occurs during the execution of a scenario, the scenario is paused. One of the following then occurs:

For more information on incomplete executions, see View and resolve incomplete executions in Adobe Workfront Fusion.

For more information on scheduling, see Schedule a scenario in Adobe Workfront Fusion.

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.

For more information about displaying information, see Scenario execution flow in Adobe Workfront Fusion.

Enable data loss

This option has to do with enabling data loss if Workfront Fusion fails to save a bundle to the queue of View and resolve incomplete executions in Adobe Workfront Fusion (for example, due to a lack of free space). With this option enabled, the data is lost in order to prevent interruptions in the overall scenario execution. This is useful for scenarios where the highest priority is continuous execution and the incoming erroneous data is not that important.

Beyond that, when executing a scenario, a module can sometimes encounter a file that is larger than the maximum allowed size. In this case, Workfront Fusion proceeds in accordance with the setting of the Enable data loss option and a warning message is shown.

For more information about maximum file size, see About mapping files in Adobe Workfront Fusion.

For more information on warnings, see Error processing in Adobe Workfront Fusion.

Auto commit

The Auto commit settings applies to transactions and defines 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).

For more information on transactions, see Scenario execution, cycles, and phases in Adobe Workfront Fusion.

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.

INFO

Examples: Workfront > Watch record watches for new issues that come in, and Workfront >Convert object converts the new request into a project and assigns it the appropriate template.

A more cycles setting is applied only when you schedule your scenario execution. When you use the Run once button, cycle settings are taken into account.

Max number of cycles is set to 1 (default) max-number-of-cycles-is-set-to-1-(default)

The Maximum number of returned files in the Workfront >Watch records module is set to 10.
If 100 requests are submitted to Workfront, and the Limit field is set to 10, then 90 files are left unprocessed after one scenario run. The next 10 files are processed in the next scheduled scenario execution.

Max number of cycles is set to 10 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 are 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 1 scenario run.

You can see the already-run cycles in the Scenario details:

For more information about this page, see Scenario details in Adobe Workfront Fusion.

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).

For more information on errors, see Error processing in Adobe Workfront Fusion.