Concurrency support for Service Bus built-in connector in Logic Apps Standard

Hi DivSwa and apseth 

We are using stateful logic apps standard workflows in ASE environment with the trigger "On single new message from queue session" and seeing some unexpected behaviors. Can you please clarify on the below items?

1. We can see concurrency option under trigger settings. So is this concurrency for multiple sessions or for a single session? If the queue has 100 different active sessions, then does this settings decides how many different session instances should it run?

2. Many times we pushed a single message to the session queue and we are seeing our workflow running 3 instances at the same on the same message? If there is one active session in queue, then it is always one instance against a session not multiple right. When we check run history of all the 3 runs picking the single message as sessionid, messageid and sequence number are same for all the 3 runs. it is not happening all the times and it happens randomly.

3. We assume this trigger works on peak lock mode though it does not mention in the name of the trigger otherwise the complete message should fail but in our case complete message and close session are successful hence we are thinking it is peak lock trigger - please confirm

Our workflow is simple trigger gets a single message, process the message, complete the message and close the session. And also we have increased the lock timeout to 5 minutes so it is not the issue with logic app processing times.

Appreciate your reply.

Thanks

JB