Azure function published but not running, "no data available"

Question

I can publish a Azure function from Visual Studio without an error.

This funtion is set to run every 4 seconds ("*/4 * * * * *") but it is not running at all. Even if I try to run it manually it do not run and show the following error:

Status: 404 Not Found

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

Under monitoring it do not shows data, under success or error count it says no data available :(

Nothing is working please help

Answer 1

This is a pretty old thread but in case anyone is facing the same issue after migrating their Function App to .NET Core 3.1, check that you have also updated the Function Runtime Version to 3. Update the Function App SDK and in Azure portal check that the function runtime settings is 3. Without updating this setting the same 404 error appears whenever you try to call your function app.

For changing the Function Runtime Version open the Function App in Azure Portal then go to Configuration -> Function runtime settings. From the Runtime version dropdown choose ~3.

Answer 2

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

According to your 404 error message, it means your function source couldn’t be found. Such as wrong resource path , function name has been changed, wrong function name or the function has been deleted.You could check whether your class name and FunctionName attribute name are consistant. If you have changed code, remeber to rebuild the project.

And please make sure you could run the Azure function successfully in Visual studio before published to Azure. In debug mode, check whether output logs are correct.

Under monitoring it do not shows data, under success or error count it says no data available

This info usually means function has never been triggered before. If you create a new function in Azure and click Monitor directly, you could also see this info. To solve this problem, unless you could trigger this Azure function successfully.