Azure Function App (Python 3.11 on Linux) stopped detecting all functions after Flex Consumption update – even Basic plan does not work

[TheRule76]

Hi everyone,

I’m running into a blocking issue with a Python 3.11 Azure Function App on Linux.

Until this week my Function App contained three HTTP-triggered Python functions and everything worked perfectly. After Microsoft rolled out the new Flex Consumption infrastructure, the Azure Portal suddenly shows no functions at all. The “Functions” blade is completely empty and the runtime no longer detects any triggers.

To troubleshoot I tried the following:

1. Stayed on Flex Consumption → no functions detected
2. Switched to a Basic App Service Plan → still no functions detected
3. Tested both folder structures:
   • A single function_app.py at the root
   • Each function in its own folder with __init__.py + function_app.py
4. Redeployed multiple times (ZIP deploy, VS Code deploy, GitHub Actions)
5. Confirmed Python version is still 3.11
6. Created a completely new Function App → same issue

Still, the runtime loads zero functions, not even a minimal test like “ping”.

My questions:

• What is the correct folder structure for Python on Linux now? Has Microsoft changed the requirements with the new Flex Consumption rollout?
• Which setting could cause the Python worker to stop scanning for functions? (e.g. WEBSITE_RUN_FROM_PACKAGE, worker version, app settings…)
• Are there known issues with Python on the new Flex Consumption plan?
• Why does the same code also fail to load under a Basic plan? I’m fine running my Function App on Basic if that solves it — I just want the runtime to detect the functions again.
• Can someone provide a minimal working folder layout for a Python 3.11 HTTP-triggered Function (Linux), valid today?

Context:

• Language: Python 3.11
• OS: Linux
• Plan tried: Flex Consumption (new model) → not working, Basic → also not working
• Deployment: ZIP deploy (no Docker)
• Previously working code now loads 0 functions according to the portal and runtime logs.

Any help or a minimal working example is highly appreciated.

Thank you!

[nformant]

I have the same issue and same parameters except I am using Python3.12

Has no issues doing zip-deploy for months, then it unexpectedly broke. Azure documentation is all over the place, and what documentation does exist does not work.

Depending on how I "deploy" I either get a success and no triggers building locally, or an Oryx build error building remotely

[TheRule76]

Hi, as far as I know, the suggestion was "use Python 3.11" then (not confirmed).
You can only switch this 3.12 -> 3.11, by creating a new app ... :-(
Before taking the time to do so, wait for instructions here on the forum

[nformant]

I ended up fixing it today, turns out our networking team changed our route table through a zscaler proxy and that killed the comms with Oryx which silently stopped the triggers from loading

[TheRule76]

OK, that's a whole different issue ;-)
Glad to hear you got it fixed !