Python Function: No HTTP triggers found, even with the sample code

Question

Hello,

I'm trying to deploy a simple python function, which worked locally. Everything seems fine, I got no errors, but no function either.

This function is being deploy in a Flex Consumption Function App, with 512mb memory in the East US 2 region, runtime stack Python - 3.

What I see in VSCode's output is:

12:22:47 PM elysium-feeds: Querying triggers...
12:22:50 PM elysium-feeds: No HTTP triggers found.

I tried manually uploading the zip file, same results.

And, as an act of desperation, I tried the same with the sample code (when you do Start Project in VSCode), and the same happened.

What am I doing wrong?

Thanks in advance,
Max

asddas

Answer 1

Hi @Maximiliano Kolus ,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

With the information provided, please check below possible causes.

• In when deploying in Azure functions, AzureWebJobsStorage is mandatory. Please check if environment variable is present and is accessible to function app from networking standpoint.
• Confirm if folder structure is correct. Are you using V1 or V2 programming model.
• Check below Environment variables are present:
  • FUNCTIONS_WORKER_RUNTIME=python
  • FUNCTIONS_EXTENSION_VERSION
  • AzureWebJobsStorage
• Check for errors in Log Stream.
  • Open Function App → Log stream
  • Restart the app
  • Look for Logs/Errors. Share if any.
• Remote build installs dependencies strictly from requirements.txt When remote build (Oryx / SCM build) is used, Azure Functions installs Python packages only from the deployed requirements.txt. If a dependency used by the function is missing or incompatible, the Python worker can fail during startup/import, which prevents trigger indexing and results in “No HTTP triggers found”.
• requirements.txt must be present at the app root and included in the deployment artifact During remote build, Oryx looks for requirements.txt at the root of the Function App (/home/site/wwwroot). If the file is missing, misplaced, or excluded from the deployment package, dependencies are not installed, causing startup failures and no trigger discovery after deployment.

If still facing issue, I have reached out to you in Private message regarding some information needed for further analysis. Please check and provide the details.