I have an Azure functions application performing background jobs for my web site. Some jobs start by demand. To achieve that I use a single HTTP trigger function calling it from web server, providing job details. The function starts a corresponding orchestration and returns a check status response. It works well in test environment but in production some requests fail. Unfortunately I do not know the response code: there is no appropriate logging for now. But I think it could be due to big number of requests.

My question is: is it a good approach to start jobs by demand? How many requests can Azure function app. handle? Maybe it is better to put requests into a queue on web server and make a queue trigger in Azure?

The runtime version of my Azure application is 4.28.4.4 targeting .NET 6.0, with “in-process” model. Pricing plan is “Premium v3 P1V3”.
Thank you in advance!