3.0 Execution Modes for BPMN Actions

For each BPMN action configurable within the processes (Figure 1), one of the following execution modes can be selected:
Figure 1
- Standard -> the action is executed the moment the process reaches the Action Task where it is configured; naturally, the process always waits for the action to complete before proceeding with the subsequent actions defined in the flow.
- Background -> the execution of the action is delegated to a cron job or worker; therefore, it is not executed the moment the process reaches the Action Task where it is configured but is instead placed into a specific queue. Naturally, the process still waits for the action to complete before proceeding with the subsequent actions defined in the flow; consequently, in this specific case, this constitutes a genuine "interruption" of the process.
It is recommended to use this mode in the following scenarios:
- when you need to execute an action that may affect a significant number of records. 
For example, a Cycle Related Records action followed by an Update Entity action executed on 100 records.
- when you need to execute an action involving a relatively small number of records, but updating those records triggers additional processes. 
For example, a Cycle Related Records action followed by an Update Entity action executed on 20 records, where each updated record triggers one or more additional processes.
- when you need to execute multiple actions in sequence that, taken together, may require several seconds to complete, potentially leaving the browser page unresponsive. 
For example, a workflow containing a combination of Create Entity, Update Entity, Send Email, Send Notification, validation checks, and their corresponding gateways.
Whenever Background mode is selected, the system immediately closes the loading page and displays the detail view of the record you were working on, together with an "Updating..." message (Figure 2).
Figure 2