This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 76%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERJ%3C/text%3E%3C/svg%3E)
Hi,
Sometimes I see that just an initialization of a variable in a Logic App (Consumption) takes more then 10 seconds. Not just once but very often I saw that behavior.
Can anyone explain this? (RunID = 08584918875000017742867045231CU242)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 87%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMU%3C/text%3E%3C/svg%3E)
Hi @Rob Joosen - Consumption SKU runs on multitenant environment where overall CPU/memory resources are shared by other apps. It could just be that the multitenancy could be the cause. I'd like to take a closer look into your app though so I'll reach out via private messaging for more info.
@Rob Joosen Thanks for providing additional info via private messages. I confirmed that there were no platform issues during the timeframe that you observed the above. As such, this is likely caused by the multitenancy aspect of Consumption SKU. If this is causing any problems, please consider switching to Standard SKU and running your workflow under a hosting SKU dedicated CPU/Memory resources.
Hi Rob Joosen,
Thank you for reaching out on Microsoft Q&A!
Logic App actions are, just as triggers etc., placed on a queue. So the processing time itself is not that long, but the lead time can be. If you look at the run details you can check the actual execution times as well as lead times. Unfortunately, this is something to cope with and not something you can configure.
If you need more control over this queueing, you can change to Logic App Standard, which provides you with reserved resources to speed things up. However, keep in mind that this has other pros and cons, such as fixed pricing per month (which can be higher than Consumption Apps) and resource limits when your logic isn't built correctly (hanging the process basically).
So that's the consideration: can you wait for it then Consumption will be okay. If you need speedy responses you can try to revert to Logic App Standard, or even: no Logic Apps at all, when this is a possibility off course depending on your scenario.
Please click “Accept answer” if you find this helpful. Feel free to drop additional queries in the comments below!
Kind regards,
Sonny