Processing orchestration jobs sequentially
You can use the Process Orchestration Jobs Sequentially option when an orchestration contains activities that can conflict with each other when multiple instances of the orchestration are running. An instance of an orchestration is also known as an orchestration job.
About this task
- An insertion into the database occurs, triggering the first instance of the orchestration to be created.
- The first instance of the orchestration starts processing the insert branch of the Pick activity.
- Before Get Inserted Rows activity completes in the first orchestration instance, a deletion in the database occurs triggering a second instance of the orchestration to be created.
- The second instance of the orchestration starts processing the delete branch of the Pick activity.
This is undesirable behavior because first instance of the orchestration (that is processing the Get Inserted Rows activity) should complete before the second instance of the orchestration starts to process the Get Inserted Rows activity to avoid a potential primary key exception in the database. These database actions should occur sequentially. To force the instances of the orchestration to run sequentially, select the Process Orchestration Jobs Sequentially check box for the orchestration. With this option set, the instances of the orchestration are run one at a time and conflicts, like primary key exceptions, are avoided.
Complete the following steps to set all jobs to run in a single instance check box.
Procedure
- Select the Project tab and expand the Orchestrations folder.
- To open an orchestration, double-click an orchestration in the Orchestrations folder. The orchestration is displayed.
- If the orchestration options are not displayed the bottom part of the orchestration tab, select from the toolbar menu.
- Select the Process Orchestration Jobs Sequentially check box. This option is automatically selected if the orchestration contains shared variables.