Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Update Data step failing on concurrent updates

Kanwaljit
Level 4
Level 4

Hi,

We have a AC6 6.1.1 with build number : 8594. It has an UPDATe STEP that is trying to insert-or-update into a AC6's own database ( no FDA being used here for this update data step).

This step is in a campaign workflow that has two instance that are trying to update the same row in the same table. But it is throwing an error.

Is there a way, we can enable either a WAIT+QUEUE or a concurrency check to wait in the step till the database lock is available. Is this a configuration ?

/Regards

Kanwal

1 Accepted Solution
Adhiyan
Correct answer by
Employee
Employee

Hi Kanwaljit,

The solution here could be to use a concurrency check for the workflow instance by using an instance variable called isRunning.

Instance variables are shared by all the parallel executions of the workflows.

Here is a simple test workflow:

The scheduler is triggering an event every minute. The next test activity is going to test the isRunning instance variable to decide

whether or not to continue the execution:

Note: isRunning is the variable name I've chosen for this example. This is not a built-in variable.

Then the activity immediately following the test in the yes branch must set the instance variable in its Initialization script:

instance.vars.isRunning = true

Finally the very last activity in the yes branch must revert the variable to false in its Initialization script:

instance.vars.isRunning = false

Regards,

Adhiyan

View solution in original post

6 Replies
deepikas1826242
Employee
Employee

Hi Kanwal,

This functionality is not available currently OOB.

Adobe recommends to improve the design of workflows so that multiple workflows do not try to improve the same schema at the same time.

Thanks,

Deepika

Adhiyan
Correct answer by
Employee
Employee

Hi Kanwaljit,

The solution here could be to use a concurrency check for the workflow instance by using an instance variable called isRunning.

Instance variables are shared by all the parallel executions of the workflows.

Here is a simple test workflow:

The scheduler is triggering an event every minute. The next test activity is going to test the isRunning instance variable to decide

whether or not to continue the execution:

Note: isRunning is the variable name I've chosen for this example. This is not a built-in variable.

Then the activity immediately following the test in the yes branch must set the instance variable in its Initialization script:

instance.vars.isRunning = true

Finally the very last activity in the yes branch must revert the variable to false in its Initialization script:

instance.vars.isRunning = false

Regards,

Adhiyan

View solution in original post

Adhiyan
Employee
Employee

Test workflow :

1526371_pastedImage_1.png

Set up the instance variable:

1526370_pastedImage_0.png

Amit_Kumar
Community Advisor
Community Advisor

Hi Kanwaljit,

In Adobe campaign there is no configuration available to enforce locks, you can use SQL activity to use SQL code to use locking if required.

Now you have two option, either change the workflow design to prevent this from happening or you can use below approach, which will cover some use cases with obvious performance tradeoffs.

1. Reduce batch size i.e to 100

1529688_pastedImage_0.png

2. Use Update records systematically

1529693_pastedImage_2.png

this should be able to fix your issue but redesigning the workflow should be the ideal solution.

lukkyluke
Level 3
Level 3

Hello,

I have implemented your suggested solution into one workflow. However I get problems as soon as the workflow gets paused due to an error. In such scenarios the isRunning variable is still set to true even after restart. Is there any way to auto-reset the instance variables in a workflow when the restart-button is clicked?

lukkyluke
Level 3
Level 3

Solved by setting the isRunning-variable to false in the advanced tab in the scheduler-activity. This is code is only triggered upon restart/start and not by "execute pending tasks now"