Worker failing without raising error about azure-functions-dotnet-worker HOT 3 OPEN

@winterlimelight Is there a specific reason your app is set to 32 bits? For better cold start perf, we recommend using 64 bit platform setting (and deploying your app payload for win-64 rid)

For the error you mentioned, a support ticket might be appropriate for the team to investigate this further.

from azure-functions-dotnet-worker.

I've not adjusted the defaults with respect to bitness/platform. That is something I can look into, but seems less likely to be relevant to the issue. I'll consider a support ticket, but if I'm being honest, I've not had much success with that route in the past.

from azure-functions-dotnet-worker.

Following extensive back-and-forth with Azure Support we received information on a probable root cause. The Azure Team identified an "issue regarding the specialized placeholders for certain apps recycling due to a DotNet JIT install state inconsistency" which they are rolling out a fix for.

There is a workaround, which is to set the application setting WEBSITE_USE_PLACEHOLDER to 0 within the app's configuration. From my read of https://learn.microsoft.com/en-us/azure/azure-functions/functions-app-settings, this will disable a certain cold start optimization in the Consumption plan.

We are still waiting four our success criteria to be met (it's not a clear pass/fail having been an intermittent issue) before considering this to be resolved, however this may be useful to anyone else with a similar problem.

from azure-functions-dotnet-worker.