Azure function does not act the same in local execution as it does in Azure cloud deployment

JustinRL 1

I have an azure function (queueTrigger) which aims to convert pdf to image completely asynchronously.
I am using Azure Core Tool in Rider to execute the code in local and the function do it job perfectly. In local the console tell me the runtime version is 3.0.14492.0 and the Hosting environment: Production

But when my function is publish in the cloud, functions are trigger asynchronously but during the file processing they all wait each other before uploading file in the azure storage. So if on file is corrupted that broke everything.

I want to know if this is a wait to have the same configuration that local execution offer into the cloud deployment app function in Azure?

Pramod Valavala 20,611 Reputation points Microsoft Employee

2020-11-24T16:21:56.673+00:00

Could you share more details on your functions and how you are performing the conversion?

Do note that functions run inside a sandbox when running on Azure. It is possible you are hitting a limitation.
JustinRL 1 Reputation point

2020-11-24T18:21:59.567+00:00

I am using https://products.aspose.com/pdf library whit the nuggets manager and the problem come at the SendTo method. In local execution all different triggers are processing at the same time and upload to the storage when the processing is over (approximately 20 sec for each trigger). But when deploy on Azure function app they all wait each other SendTo method return before uploading all after (so it like 1min for 3 files).

I am using version runtime v3 in Azure to deploy the function

I also don't have a lot of experience whit azure function and I have difficulty to find if some configuration setting can help me or is variable in the host.json can solve the problem because it look like they doesn't are use in the local execution?

Share via

Azure function does not act the same in local execution as it does in Azure cloud deployment