Title: Fix Azure Functions deployment (Linux Consumption, Python 3.10, Python v2 model, GitHub Actions ZIP deploy) Need: Deployment succeeds but Python v2 model functions are not discovered (missing functions / triggers don’t run) and errors appear in Log Stream. I need an experienced Azure Functions engineer to identify the root cause, fix the GitHub Actions ZIP deployment, and confirm the Function App runs correctly. Stack: Azure Functions: Linux Consumption Runtime: Functions v4 Language: Python 3.10 Programming model: Python v2 model (decorator-based FunctionApp / function_app.py) Deploy method: GitHub Actions ZIP deploy Symptoms (one or more): Functions not visible / “no functions found” Triggers not firing Worker/import/indexing errors in Log Stream I will provide: GitHub Actions logs (deploy step output) Azure Portal Log Stream output (and App Insights traces if enabled) Function App configuration (App Settings names, values masked) Repo structure summary (where host.json, requirements.txt, function_app.py live) What “done” means: Deploy works reliably from main Python v2 functions are indexed and visible Triggers run successfully (HTTP/Timer/etc.) Short write-up: root cause + fixes applied (pipeline + settings) + how to avoid it Engagement: Fixed price for 1–2 hour diagnosis Extend only if needed after diagnosis Please include in your reply: 1–2 examples where you fixed Python Azure Functions v2 model deployment issues on Linux Consumption Your approach to: verifying ZIP package root structure (e.g., host.json at ZIP root, no extra folder layer) ensuring dependencies install correctly (requirements.txt, remote build vs packaged deps) confirming v2 model indexing (worker indexing / relevant app settings) Screening questions (answer briefly): What setting(s) do you check for Python v2 model indexing on Azure Functions v4? What’s the most common ZIP packaging mistake that causes “functions not found”? Where do you check first for worker startup/import errors and why?