Dennis Admin hi & thanks for join me here at Q&A portal,
this smells like Functions host startup failure, not ur Durable code directly. web_host.lifecycle = Healthy and webjobs.storage = Healthy, but script_host.lifecycle = Unhealthy / NoScriptHost means the platform container is up and storage is reachable, but the Python worker/script host never loaded the app. Since the same code base broke in 3 resource groups on same day, I would suspect runtime/platform image update, Python version mismatch, dependency restore/import failure, or Flex Consumption compatibility regression. Check App Insights traces around startup for Host startup, Worker failed to start, ModuleNotFoundError, ImportError, language worker, or python. Also verify app settings: FUNCTIONS_WORKER_RUNTIME=python, Python version, AzureWebJobsStorage, Durable extension bundle, and package/deployment mode. Quick isolation: redeploy the last known good package, restart app, and temporarily pin/change Python runtime version if possible. If startup logs show no app-level import error and all 3 apps fail identically, open Azure Functions support with UTC timestamp and mention Flex Consumption + Python + NoScriptHost started without code/resource changes across multiple apps.
host is alive but script host does not start, look at startup/import/runtime logs, likely platform/runtime regression if replicated across 3 apps.
rgds,
Alex
&
If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal