Linux Consumption Function App stuck with 0 running workers for 24+ hours - reproduces across regions, plans, storage accounts, and runtimes

Question

Linux Consumption Function App stuck with 0 running workers for 24+ hours - reproduces across regions, plans, storage accounts, and runtimes

Tims 20

I'm trying to get a brand-new Linux Consumption (Y1) Function App running and it never successfully starts — Azure's own built-in diagnostics confirm 0 running workers for over 24 hours straight, and this reproduces no matter what I change.

The app's SCM/Kudu site (https://<app>.scm.azurewebsites.net) returns a blank "The service is unavailable" page — confirmed both in a browser and via API calls, so it's not a client-side issue.
The Portal's own Overview page shows "Runtime version: Error" instead of an actual version.
The Functions list in the Portal shows "We were not able to load some functions in the list due to errors."
Using the Portal's "Diagnose and solve problems" > "Function App Down or Reporting Errors" report, the "Functions that are not triggering" check shows: "Function was running on 0 worker instance for more than 1420 minutes" (over 23 hours) — all other checks (Python Function, Key Vault settings, deployment settings, etc.) pass cleanly.
Application Insights (linked correctly) shows zero telemetry of any kind for this app — not just no errors, no requests/traces/exceptions at all — across the whole window, meaning the host never gets far enough to log anything.

Not the issue - Since this reproduced identically every time, I've tried recreating the app under every combination below, in case one specific resource was corrupted or stuck:

Deleted and recreated the Function App itself (same name), 4 times.
Deleted and recreated the underlying Consumption hosting plan too, not just the app.
Two different regions (South Africa North, then North Europe).
Two different, completely fresh storage accounts for AzureWebJobsStorage.
A completely different language runtime (a throwaway Node.js 24 app) — identical symptom, ruling out anything Python-specific.
Restarted via the Portal/CLI — no change.
Waited 15+ minutes between checks multiple times, to rule out a slow cold start.

Every single combination shows the exact same "0 workers" behaviour. Since it's independent of region, plan, storage account, and runtime, I don't think it's anything in my own configuration — it looks like the Consumption plan's scale controller simply never allocates a worker for this app/subscription.

Has anyone seen this exact "0 running workers, indefinitely" pattern before, and is there a known fix or a next diagnostic step I'm missing? Happy to share more detail (correlation IDs, resource names, etc.) if it helps.

Thank you in advance!

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

TP 163.1K Volunteer Moderator

Hi,

Have you tried running it on Flex Consumption instead? Since legacy Linux consumption is deprecated and scheduled to retire in 2028, I'm wondering if new apps are not working as a result, while existing are fine? To be clear I've not seen any official documentation to this effect, it is just speculation based on my experience over the years.

Azure Functions Consumption plan hosting (legacy)

https://learn.microsoft.com/en-us/azure/azure-functions/consumption-plan

-TP

Tims 20 Reputation points

2026-08-31T18:08:22.14+00:00

Hi TP,

Thanks — yes, I tried Flex Consumption and it worked immediately (SCM responded normally on the very first try, vs. persistent 503s across 4+ attempts on legacy Consumption). Seems consistent with your theory - appreciate the response!
TP 163.1K Reputation points Volunteer Moderator

2026-08-31T18:13:41.2533333+00:00

That's great it works on Flex. Please click Accept Answer to close up this thread.

Thank you.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Fabian Zankl 185 Reputation points

2026-08-31T18:23:59.5833333+00:00

One documentation point in support of @TP 's theory: the Azure Functions "hosting options" comparison page now lists the Consumption plan's availability as generally available on Windows but retired on Linux. That is separate from the 30 September 2028 date, which concerns when hosting for existing Linux Consumption apps ends. There is still no official statement that newly created Linux Consumption apps no longer receive workers, so this stays circumstantial, but the availability label plus your result line up. The same symptom was reported on another thread two days ago on a fresh free trial across three regions. If you kept the correlation IDs, a support case is the way to get an authoritative answer on whether this is intended behaviour or a documentation lag.

https://learn.microsoft.com/en-us/azure/azure-functions/functions-scale