Liquid Transformation JSON to JSON action slow on first call

Category: azure logic apps


sanjaybhagia on Fri, 26 Jul 2019 22:51:49


I have a simple logic app where I have a liquid transformation action (json to json). liquid file exists in intergration account. The Logic app is http triggered. On the first call, this transformation action seems to take quite a long time. From my tests, the app takes about 16-17 seconds on that particular action. If i make the next call immediately after that, the same action is executed in about 1 second. The payload is not that big either (it's a json array of just two items with 5-6 properties with pretty straight forward mapping - not even any custom filters etc.)

Both the resource (Logic App and Integration Account) are in same region (Australia East). 

For comparison, I created another app in the same resource group which has similar transformation action using the same intergration account. If I make call to the second app (after calling the first app), it is executing faster. So I belive, it is the integration account that is taking some time to warm up on first call. 

I have tested the Integration Account with Free tier - Is there any limitation on free tier when it comes to performance?

I have tried to find out documentation but no luck. I have been trying to find out if there is any cold start in Logic apps (in any situation) but didn't come across any material. There is alot on this topic for Azure functions.




PramodValavala-MSFT on Mon, 29 Jul 2019 07:16:17

The free tier is meant just for development scenarios. It is not bound by any SLA and is NOT recommended for production use cases.

You can read more about more about integration account in the docs and also reference the limits that they posses.

sanjaybhagia on Tue, 30 Jul 2019 06:59:20

makes sense. Thanks for explanation