Run Action Concurrency

hyudolee

Hi, I want to check the action concurrency.

If several users run the action, Action which first user run will run?

The second user's will not run?

rob_marshall

@hyudolee @Misbah 

 

Yes, when running the same action by multiple people at the same time, the actions essentially get put in a queue and the first one runs to completion, and then the second one.  This is one of the main reasons we suggest against having end-users run actions (5.01-03).  And yes, if multiple people are trying to update the exact same cell by running an action, the last one that runs wins.

 

Rob

Misbah

@hyudolee 

 

Good question!

 

My understanding is that if  end users (with enabled selective access and other security measures) run the action at the same time it runs every body's action successfully. However I still believe that Anaplan doesn't run the action concurrently and it runs them sequentially. I might be wrong 

 

On the other end if end users with same access or WSA admins run the action at the same time then whosoever runs the action last will be saved and all other preceding actions will be overridden. Also as soon as the import is run the model locks itself for end users until the action is successfully completed

 

Misbah

Miz Logix

hyudolee

Hi, @rob_marshall and @Misbah.

 

Thanks for replay!

I understand that Action runs in order.

 

How about Process Action?

Action in Process will never run across?

 

Misbah

@hyudolee 

 

Process is nothing but the collection of actions that are supposed to run in a chronological manner. Basics will still be the same which is what Rob had mentioned. 

 

Thanks,

Misbah

<Miz Logix>

TristanS

Just to add a comment on the question related to process execution and concurrency of actions within a process. The way actions are queued when the same process is executed simultaneously is a bit interesting. For example, if you have Process A with the following actions:

• Action 1
• Action 2
• Action 3

Process A usually takes 50 seconds on average to execute.

So if user 1 ran process A now then 20 seconds after user 2 runs process A as well. The actions don't queue up the way you would expect. What you would normally expect is as follows:

• User 1 Action 1
• User 1 Action 2
• User 1 Action 3
• User 2 Action 1
• User 2 Action 2
• User 2 Action 3

What I've seen after we checked the audit logs is something like as follows:

• User 1 Action 1
• User 1 Action 2
• User 2 Action 1
• User 1 Action 3
• User 2 Action 2
• User 2 Action 3

Sometimes you would even get

• User 1 Action 1
• User 2 Action 1
• User 1 Action 2
• User 2 Action 2
• User 1 Action 3
• User 2 Action 3

So be careful when creating user activated processes as it can cause a lot of problems when you have sequence dependent actions executing as what I've experienced.