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