Configure scenario settings
You can configure specific settings for scenarios in the scenario settings panel.
Access requirements
You must have the following access to use the functionality in this article:
| table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 layout-auto html-authored no-header | |
|---|---|
| Adobe Workfront plan | Any |
| Adobe Workfront license |
New: Standard Or Current: Work or higher |
| Adobe Workfront Fusion license** |
Current: No Workfront Fusion license requirement. Or Legacy: Any |
| Product |
New:
Or Current: Your organization must purchase Adobe Workfront Fusion. |
| Access level configurations* |
You must be a Workfront Fusion administrator for your organization. You must be a Workfront Fusion administrator for your team. |
For more detail about the information in this table, see Access requirements in Workfront documentation.
For information on Adobe Workfront Fusion licenses, see Adobe Workfront Fusion licenses.
Open the scenario settings
-
Click Scenarios in the left panel.
-
Find the scenario you want, then click the name.
-
Click anywhere on the scenario to enter the scenario editor.
-
Click the gear icon near the lower-left corner of the page.
In the Scenario settings panel that displays, you can configure various advanced settings for the scenario.
-
Enable or disable the Scenario settings as needed. See Scenario settings options below.
Scenario settings options
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:
-
If the Sequential processing option is enabled, Workfront Fusion stops processing the pre-existing sequence until all incomplete executions are resolved.
-
If the Sequential processing option is disabled, the scenario continues to run according to its schedule, accompanied by repeated attempts to rerun the incomplete executions.
For more information on incomplete executions, see View and resolve incomplete executions.
note note NOTE Sequential processing may cause a delay in the execution of a scenario. If there are incomplete executions still in the queue when an instant scenario triggers or a scheduled scenario is set to execute, that scenario will execute after all of the executions before it in the queue are complete. If the use case for your scenarios does not require sequential processing, we recommend disabling the sequential processing option. For more information on scheduling, see Schedule a scenario.
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.
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 the incomplete execustion folder. 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.
For more information on incomplete executions, see View and resolve incomplete executions.
Enable data loss
This option has to do with enabling data loss if Workfront Fusion fails to save a bundle to the queue of incomplete executions (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 on incomplete executions, see View and resolve incomplete executions.
For more information about maximum file size, see Fusion performance guardrails.
For more information on warnings, see Error types.
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).
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.
For more information on polling triggers, see Polling triggers in the article Module overview.
-
If the scenario starts with an instant trigger, the setting is ignored and all the pending events are processed during a single scenario execution, one event per one cycle.
For more information on instant triggers, see Instant triggers in the article Module overview.
-
If the scenario does not start with a trigger (instant/polling), the specified maximum number of cycles is always performed.
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)
The Max number of cycles in the Workfront > Watch records module is set to 10.
If 100 requests are submitted to Workfront, and the Max number of cycles 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
The Max number of cycles in the Workfront > Watch records module is set to 10.
If 100 files are added to the Dropbox folder and the Max number of cycles 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.
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 types.