Azure logic app concurrent thread execution

Question

Hi Expert ,
I am looking for some idea before selecting exact plan type for logic apps. Our logic app will be mostly http or webhook based. When going through different documents available can find various different with standard & Consumption based logic app but what I am looking for

1) What is the concurrent thread logic app can run ? For example since its webhook based so multiple end system can call this logic app , so is there any limit on concurrent thread execution in logic app ?

2) If we implement using Queue based (storage queue or service bus) , can we control on number of message being picked up by logic app in one run. Example , at some point of time in service bus there is 20 message , but in logic app wants to pickup at max 10 message in single run ?

Thank you in advance.

Thanks!

Answer 1

@Baharul Islam Thanks for reaching out. Yes, there is a throughput limit for different logic app SKU and you can refer to this document for more details. There are different types of limit you may hit when you are in a multi-tenant environment (consumption SKU) as documented.

What is the concurrent thread logic app can run ? For example since its webhook based so multiple end system can call this logic app , so is there any limit on concurrent thread execution in logic app ?
As per the document for logic app consumption you can have 1000 calls parallelly (i.e. inbound calls) whereas for standard there is no limit.

If we implement using Queue based (storage queue or service bus) , can we control on number of message being picked up by logic app in one run. Example , at some point of time in service bus there is 20 message , but in logic app wants to pickup at max 10 message in single run ?
The logic app will get executed as soon as there is any message in the storage queue or service bus queue/subscription. Depending on the action that you are using you need to review the action property of that connector whether it provides any property to limit the max number of messages per execution.
For service bus standard, you can leverage the Maximum message count property to limit the number of messages received from the service bus but in case of consumption there is no option. The result will be an array so you can enable the Split On property (under the Settings section) for the standard SKU service bus connector.

In case if you are looking for limit the parallel execution of your workflow then you can limit it by leveraging the Concurrency Control property of your trigger. For more details please refer to this section.