azure-functions-dotnet-worker: Functions not found in Azure after nuget update

If you are experiencing the “No job functions found” error when using Microsoft.Azure.Functions.Worker.Sdk 1.16.X and your function app is running on an app service environment, add the below app setting to your app and that will fix the issue.

Name: AzureWebJobsFeatureFlags Value: EnableWorkerIndexing

The next version of host update will have this app setting baked into it.

If you are experiencing an issue on another platform, please open a new issue with details specific to your issue.

If you are experiencing the “No job functions found” error when using Microsoft.Azure.Functions.Worker.Sdk 1.16.X and your function app is running on an app service environment, add the below app setting to your app and that will fix the issue.

Name: AzureWebJobsFeatureFlags Value: EnableWorkerIndexing

The next version of host update will have this app setting baked into it.

If you are experiencing an issue on another platform, please open a new issue with details specific to your issue.

Thank you for the response.

The workaround indeed seems to solve the issue; however we would rather wait for the update.

Is there any ETA on this update?

I just tested again, and it appears to be working now.

My Azure App Service Function host now reports: Runtime version: 4.28.3.3

And it works with both version 1.6.2 and 1.6.4 without having to explicitly set any flags.

1.16.2 works perfectly locally running in Visual Studio (so nothing needs changing in the local.settings.json since locally its running fine)

I added “AzureWebJobsFeatureFlags”: “EnableWorkerIndexing” to the local.settings.json but as expected it made no difference (still works locally but still fails to load functions in Azure)

Clearly a breaking change has been introduced at 1.16.x making it fail to load functions when running in Azure (just changing the 1.16.x back to 1.15.1 and everything works perfectly in Azure)

                       Jason

From: Justin @.> Sent: Saturday, December 2, 2023 12:28 AM To: Azure/azure-functions-dotnet-worker @.> Cc: Jason Wilby @.>; Mention @.> Subject: Re: [Azure/azure-functions-dotnet-worker] Functions not found in Azure after nuget update (Issue #2070)

You don’t often get email from @.@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification [EXTERNAL]

Ran into this error running in visual studio. 1.15.1 works without any local.settings.json file. 1.16.1-3 fails without any local.settings.json file. Add local.setting.json file with specific values mentioned in #2107https://github.com/Azure/azure-functions-dotnet-worker/issues/2107 and it works again.

Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-functions-dotnet-worker/issues/2070#issuecomment-1836955552, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A67UKV4QIAZ4L6V3A6G75G3YHJYYPAVCNFSM6AAAAAA7NZI5SKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZWHE2TKNJVGI. You are receiving this because you were mentioned.Message ID: @.@.>>

IMPORTANT NOTICE: This e-mail message is intended to be received only by persons entitled to receive the confidential information it may contain. E-mail messages to clients of NWEH may contain information that is confidential and legally privileged. Please do not read, copy, forward, or store this message unless you are an intended recipient of it. If you have received this message in error, please forward it to the sender and delete it completely from your computer system.

@kshyju Great news that you have located the issue with this breaking change 👍

Two follow up questions:

1. How can we check that the hosts we use have been updated to support 1.16.x? I.e.:
   • If on 1.15.1 when can we safely upgrade to 1.16.x without needing to set the feature flag?
   • If on 1.16.2 with feature flag – when can we remove this temporary feature flag?
2. How do you intent to prevent something like this happening in the future? On the surface it seems a little crazy that you would deploy a breaking change version of Worker.Sdk to NuGet before ensuring that ALL Azure Function hosts worldwide have been updated to support the breaking change.

Confirm that we are seeing this issue as well in our environments. The work around of <FunctionsEnableWorkerIndexing>False</FunctionsEnableWorkerIndexing> is working and we’re redeploying to all of our environments.

Here is our App Hosting Details

• Azure North Central US
• OS Windows
• SKU P1v2
• Runtime: 4.27.5.21549
• Stack: .NET - v6.0

I believe this is the root cause of the issue https://github.com/Azure/azure-functions-dotnet-worker/pull/1968#issuecomment-1787998486

@kshyju 2023-10-24T13:46:22.2923249+00:00 34278435-7031-44b9-9cde-1cbb40d2843b North Central US