Scenario execution, cycles, and phases in Adobe Workfront Fusion

Adobe Workfront Fusion is a transactional system, similar to relational databases. Each scenario execution starts with the initialization phase, continues with at least one cycle composed of the operation and commit/rollback phases, and ends with the finalization phase:




Cycle #1

Operation (reading or writing)

Commit or rollback

Cycle #2

Operation (reading or writing)

Commit or rollback

Cycle #N

Operation (reading or writing)

Commit or rollback


Access requirements

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

Adobe Workfront plan*

Pro or higher

Adobe Workfront license*

Plan, Work

Adobe Workfront Fusion license**

Workfront Fusion for Work Automation and Integration

Workfront Fusion for Work Automation

Product Your organization must purchase Adobe Workfront Fusion as well as Adobe Workfront to use functionality described 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.


During the initialization phase, all necessary connections (connection to a database, email service, and so on) are created. They are also checked if each module is capable of performing their intended operations.


Each cycle represents an undividable unit of work composed of a series of operations. It is possible to set the maximum number of cycles in the scenario settings panel. The default number is 1.

For more information, see The scenario settings panel in Adobe Workfront Fusion.


During the operation phase reading and/or writing operation is performed:

  • The reading operation consists of obtaining data from a service that is then processed by other modules according to a predefined scenario. For example, the Dropbox >Watch files module returns new bundles (files) created since the last scenario execution.
  • The writing operation consists of sending data to a given service for further processing. For example, the Dropbox >Upload a file module uploads a file to a Dropbox folder.


If the operation phase is successful for all modules, the commit phase begins during which all operations performed by the modules are committed. This means that Workfront Fusion sends information to all the services involved in the operation phase about its success.


If an error occurs during the operation or commit phase on any module, the phase is aborted and the rollback phase is started, making all operations during the given cycle void. Some modules do not support rollback and operations performed by these modules cannot be taken back. For more information see the ACID modules section.


During the finalization phase, open connections (for example, FTP connections, database connections, and so on) are closed and the scenario is completed.

ACID modules

All Workfront Fusion modules that support rollback (also known as transactionality) are marked with the ACID tag.

Modules not marked with this tag cannot be reverted back to their initial state when errors occur in other modules. A typical example of a non-ACID module is the Email >Send an Email action. After the email is sent you cannot undo the sending.

On this page