Function App Function Execution Count at zero

Question

Function App Function Execution Count at zero

Cheah, Felix FC 20

I have a function app with several functionthat is triggered when there's a new file in a blob storage. User's image

For some reason the metric "Function Execution Count" keeps going to zero. I've checked individual function and have seen they have defeintely run. I've also looked in the log analytics workspace and can see the functions running. Any reason why the Function Execution Count is showing zero? I use this metric to alert me and the fuction app isn't running

User's image

Victor Gruber 81 Reputation points

2025-05-05T01:32:14.4433333+00:00

Use environment variables to store the value after running the function to avoid the count going back to zero
Cheah, Felix FC 20 Reputation points

2025-05-05T03:30:46.1933333+00:00

How do i do that?
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.
Praveen Kumar Gudipudi 1,875 Reputation points Microsoft External Staff Moderator

2025-05-08T16:59:41.3233333+00:00
Cheah, Felix FC,

From backend logs we are able to see Daily Cap Quota impacted for you application insights.

Critical Resource Alert



⚠️ LA Daily Cap Reached - OverQuota

The Application Insights resource resourcename is configured to send telemetry to the Log Analytics workspace with the resource URI /subscriptions/XXXXX-XXXX-XXXX-XXXX-XXXXXXXX/resourceGroups/ResourceGroupName/providers/Microsoft.OperationalInsights/workspaces/log-XXXX-XXx-xxxx. However, the latest Log Analytics snapshot captured at 5/8/2025 12:00:38 PM UTC (4 hours ago) reports that you has reached Daily Cap limit in Log Analytics.

Daily Cap OverQuota Impact:

The backend Log Analytics resource has already ingested data up to the configured LA Daily Cap setting.

Any new data, including Application Insights telemetry, sent to this LA workspace may be getting dropped currently.

Telemetry ingestion will be paused until the LA Daily Cap reset hour at 16:00 UTC.

To resolve this:

You should either remove or increase the Daily Cap setting for the Log Analytics resource to account for increased data.

You may also consider reducing data being sent to the LA Workspace.

For more details, refer to the troubleshooting guide.

Please check above steps and let us know with an update.
Cheah, Felix FC 20 Reputation points

2025-05-12T03:59:40.7633333+00:00

Hi,

I understand the Daily Cap is being hit every day (towards the end of the day), but shouldn't the execution count be non zero again after it's been resetted at 16:00 UTC.

It hasn't resetted after dropping to zero.
Mohan Krishna T Sreeramulu 280 Reputation points Microsoft External Staff Moderator

2025-05-14T02:08:07.04+00:00

Hi Cheah, Felix FC,

Apologies for the delay in response, the execution count should ideally resume after the Daily Cap reset at 16:00 UTC, but based on the backend logs, the Log Analytics workspace hit its quota, causing telemetry data including Application Insights logs to be dropped.

Possible Reasons Execution Count Is Still Zero

Telemetry Ingestion Delay sometimes, ingestion takes time to resume after hitting the quota, so there may be a slight lag before executions start reflecting again.

Log Analytics Workspace Quota even though the cap resets at 16:00 UTC, if new telemetry surpasses the daily quota quickly, execution count might drop to zero again.

If execution data isn't being processed correctly, verify that the Log Analytics workspace is receiving incoming telemetry.

I Suggests you recheck

Increase the Daily Cap raising the limit ensures telemetry isn’t dropped due to quota exhaustion.

Reduce Unnecessary Logs, If the application sends excessive data, consider filtering logs to avoid hitting the cap frequently.

If the function app was affected by the quota, verify whether it's still running normally.

Could you please let us know if you are still experiencing the same issue?
Cheah, Felix FC 20 Reputation points

2025-05-15T00:35:29.01+00:00

The function app seems to be running normally but the excution count is still zero.

I can definitely see logs from the app going into the log analytics workspace
Cheah, Felix FC 20 Reputation points

2025-05-15T20:33:36.13+00:00

I've also changed some configured and the daily limit is no longer being hit, but the execution count is still zero

1 answer

Your answer

Victor Gruber 81 Reputation points

2025-05-05T01:32:14.4433333+00:00

Use environment variables to store the value after running the function to avoid the count going back to zero
Cheah, Felix FC 20 Reputation points

2025-05-05T03:30:46.1933333+00:00

How do i do that?
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.
Praveen Kumar Gudipudi 1,875 Reputation points Microsoft External Staff Moderator

2025-05-08T16:59:41.3233333+00:00

Cheah, Felix FC,

From backend logs we are able to see Daily Cap Quota impacted for you application insights.

Critical Resource Alert



⚠️ LA Daily Cap Reached - OverQuota

The Application Insights resource resourcename is configured to send telemetry to the Log Analytics workspace with the resource URI /subscriptions/XXXXX-XXXX-XXXX-XXXX-XXXXXXXX/resourceGroups/ResourceGroupName/providers/Microsoft.OperationalInsights/workspaces/log-XXXX-XXx-xxxx. However, the latest Log Analytics snapshot captured at 5/8/2025 12:00:38 PM UTC (4 hours ago) reports that you has reached Daily Cap limit in Log Analytics.

Daily Cap OverQuota Impact:

The backend Log Analytics resource has already ingested data up to the configured LA Daily Cap setting.

Any new data, including Application Insights telemetry, sent to this LA workspace may be getting dropped currently.

Telemetry ingestion will be paused until the LA Daily Cap reset hour at 16:00 UTC.

To resolve this:

You should either remove or increase the Daily Cap setting for the Log Analytics resource to account for increased data.

You may also consider reducing data being sent to the LA Workspace.

For more details, refer to the troubleshooting guide.

Please check above steps and let us know with an update.
Cheah, Felix FC 20 Reputation points

2025-05-12T03:59:40.7633333+00:00

Hi,

I understand the Daily Cap is being hit every day (towards the end of the day), but shouldn't the execution count be non zero again after it's been resetted at 16:00 UTC.

It hasn't resetted after dropping to zero.
Mohan Krishna T Sreeramulu 280 Reputation points Microsoft External Staff Moderator

2025-05-14T02:08:07.04+00:00

Hi Cheah, Felix FC,

Apologies for the delay in response, the execution count should ideally resume after the Daily Cap reset at 16:00 UTC, but based on the backend logs, the Log Analytics workspace hit its quota, causing telemetry data including Application Insights logs to be dropped.

Possible Reasons Execution Count Is Still Zero

Telemetry Ingestion Delay sometimes, ingestion takes time to resume after hitting the quota, so there may be a slight lag before executions start reflecting again.

Log Analytics Workspace Quota even though the cap resets at 16:00 UTC, if new telemetry surpasses the daily quota quickly, execution count might drop to zero again.

If execution data isn't being processed correctly, verify that the Log Analytics workspace is receiving incoming telemetry.

I Suggests you recheck

Increase the Daily Cap raising the limit ensures telemetry isn’t dropped due to quota exhaustion.

Reduce Unnecessary Logs, If the application sends excessive data, consider filtering logs to avoid hitting the cap frequently.

If the function app was affected by the quota, verify whether it's still running normally.

Could you please let us know if you are still experiencing the same issue?
Cheah, Felix FC 20 Reputation points

2025-05-15T00:35:29.01+00:00

The function app seems to be running normally but the excution count is still zero.

I can definitely see logs from the app going into the log analytics workspace
Cheah, Felix FC 20 Reputation points

2025-05-15T20:33:36.13+00:00

I've also changed some configured and the daily limit is no longer being hit, but the execution count is still zero

Answer 1

Madugula Jahnavi 495 Microsoft External Staff Moderator

Hello Cheah, Felix FC,

Check below troubleshooting to resolve the issue:

Add below "host.json" in your code and make changes (function name) accordingly and check if the metrics are working.

{
  "version": "2.0",
  "logging": {
    "logLevel": {
      "default": "Information",
      "Function": "Information",
      "Host.Aggregator": "Information",
      "Host.Results": "Information",
      "Function.Function1": "Information",
      "Function.Function1.User": "Information"
    }
  },
  "applicationInsights": {
    "samplingSettings": {
      "isEnabled": false
    },
    "enableLiveMetricsFilters": true
  },
  "concurrency": {
    "dynamicConcurrencyEnabled": true,
    "snapshotPersistenceEnabled": true
  }
}

Check the hosting plan of the dedicated function app and see if any one of the limitations are being hit.

You can go to the "Diagnose and solve problems" option under the Function App's resource menu contains scenario-based troubleshooting step that can be used to get more inputs on the Statistics related to function execution. Once you visit the above path, you can check for execution then it provides you the function execution counts related details.

User's image

Also, verify if you have configured and enabled the application insights properly regarding the logs and metrics part.

If the answer is helpful, please click on Accept Answer and upvote it. If you still have any queries, click on comment.

Madugula Jahnavi 495 Reputation points Microsoft External Staff Moderator

2025-05-21T07:24:13.6033333+00:00

Did you get a chance to look into the above answer! If you still have any queries, please click on comment.

Cheah, Felix FC 20

See below for the settings i have in the host.json and i can confirm wise_data_dpp is defintely running.

How do i check if the hosting plan for the function app is being limited?

The diagnose and solve problems doesn't show any issues. You can see the app has been running but the execution count metric is still 0

User's image

{
  "version": "2.0",
  "logging": {
    "applicationInsights": {
      "enableDependencyTracking": false,
      "samplingSettings": {
        "isEnabled": true,
        "maxTelemetryItemsPerSecond": 5,
        "excludedTypes": "Request"
      }
    },
    "logLevel": {
      "default": "Warning",
      "Function.wise_data_dpp": "Information"
    }
  },
  "extensionBundle": {
    "id": "Microsoft.Azure.Functions.ExtensionBundle",
    "version": "[3.*, 4.0.0)"
  },
  "functionTimeout": "00:10:00"
}

Cheah, Felix FC 20 Reputation points

2025-05-21T21:06:51.29+00:00

I can defintely see logs going into log analtyics from the the function app

These are the metrics for the App service plan

I can also see the execution count for the other app is working:
Madugula Jahnavi 495 Reputation points Microsoft External Staff Moderator

2025-05-22T04:36:03.5833333+00:00

Cheah, Felix FC, Did you check if any network or firewall that has been blocking the function app to execute externally?
Cheah, Felix FC 20 Reputation points

2025-05-22T04:40:01.33+00:00

The function app is definitely executing. Only the metric does its not
Cheah, Felix FC 20 Reputation points

2025-05-25T23:18:12.8166667+00:00

The execution count has dropped to zero again

Log analytics hasn't reached it's daily cap and i can see the function app is defintely running
Bathini Harshitha 5 Reputation points Microsoft External Staff Moderator

2025-05-27T12:21:14.36+00:00

Hi Cheah, Felix FC

The Function Execution Count shows zero despite confirmed runs, because Application Insights hit its daily telemetry cap. Once the cap is reached, it stops recording data including executions until it resets at 16:00 UTC.

Even after the daily limit resets, if your Function App sends a more data again too quickly, it can reach the limit again, and the execution count may still continue to show zero. Also, there may be a delay before new data starts showing up.

Verify by increasing the Daily Cap in your Log Analytics workspace so it can handle more telemetry data from your Function App. This change allows more data to be ingested before hitting the limit.

Set daily cap on Log Analytics workspace

To reduce telemetry volume, enable sampling in Application Insights to send only some of the data, adjust the logging level to avoid too much detail, and avoid collecting data that is not important or useful for monitoring.

Sampling in Azure Application Insights with OpenTelemetry

Make sure to regularly monitor the amount of telemetry your app sends to avoid hitting the daily limit and ensure your Function App is correctly configured to report metrics to Application Insights.

Filtering and preprocessing in the Application Insights SDK

Please do not forget to “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.
Cheah, Felix FC 20 Reputation points

2025-05-27T17:09:26.1933333+00:00

The daily cap isn't being hit anymore and the execution count is still zero
Bathini Harshitha 5 Reputation points Microsoft External Staff Moderator

2025-05-28T06:18:25.9966667+00:00
Hi Cheah, Felix FC

Since the daily cap is no longer being hit but the execution count still shows zero, the issue is likely due to telemetry not being properly ingested or queried correctly.

Check if the function is running correctly, go to your Function App in the Azure portal, open Monitor > Live Metrics Stream, and see if it shows real-time activity. If it does, the function is working, but there may be an issue with how the logs or metrics are being collected.

Verify Application Insights is connected properly, go to your Function App in the Azure portal, open Configuration > Application settings, and check that either APPINSIGHTS_INSTRUMENTATIONKEY or APPLICATIONINSIGHTS_CONNECTION_STRING is set correctly. Also, make sure the Application Insights resource still exists and has not been deleted or changed recently.

Enable Application Insights integration

Check if sampling is too aggressive or if the logging level is set too high, which may suppress execution traces. You can also go to Application Insights and run this query to check if any requests are being logged:

requests | where timestamp > ago(24h) | summarize count() by cloud_RoleName

If you see data in the logs but the execution count still shows zero, it could be a UI issue or query caching in the portal.

How to configure monitoring for Azure Functions

Try deploying the same function code to a new Function App and see if telemetry works as expected, which can help determine if the issue is app specific.

Please do not forget to “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.
Cheah, Felix FC 20 Reputation points

2025-05-28T21:01:21.75+00:00

I can see the logs in the logs analytics workspace

But it doesnt look like it shows in the invocations in the function app

In the live metrics it looks like the function app is running.

I've checked the connection string is definitely correct. Where does the instrumentationkey come from?

Application insights is definitely linked
Bathini Harshitha 5 Reputation points Microsoft External Staff Moderator

2025-05-29T11:54:55.0933333+00:00

Hi Cheah, Felix FC,

Thanks for confirming the logs, live metrics, and connection string setup. Since everything else looks correct, the reason the execution count still shows zero is likely because the Function App is not logging telemetry in the format expected by the Azure portal's "Invocations" view.

If you are using the .NET Isolated process model, you'll need to explicitly enable Application Insights integration in your code by calling AddApplicationInsights() inside the ConfigureFunctionsWorkerDefaults method in Program.cs. Without this, invocation traces will not appear in the portal, even though telemetry is being sent to Application Insights.

Application Insights

Also, ensure that sampling is not too aggressive and that no telemetry initializers are overriding the cloud_RoleName, as that can also interfere with proper display in the portal.

Sampling in Application Insights

Please do not forget to “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.
Cheah, Felix FC 20 Reputation points

2025-05-29T21:15:22.0933333+00:00

I haven't done anything and the execution count has gone up again, this has happened before and after a few days it will drop to zero again, why might this be happening? Note this function app has been running for over a year without any issues until Microsoft migrated all classic application insights to workspace-based resources.

I'm using python, how do i enable application insights through here
Bathini Harshitha 5 Reputation points Microsoft External Staff Moderator

2025-05-30T17:32:25.9066667+00:00
Hi Cheah, Felix FC

Thanks for confirming you are using Python. As you mentioned the execution count intermittently drops to zero especially after the migration to workspace-based Application Insights this typically indicates that telemetry is not being sent in a way the Azure portal expects.

In Python Function Apps, telemetry is not automatically tracked like it is in .NET, so you need to explicitly configure it using the OpenCensus SDK. To resolve this, make sure the APPLICATIONINSIGHTS_CONNECTION_STRING is configured in your application settings, and add the following code in __init__.py to ensure logs are forwarded to Application Insights.

import os import logging from opencensus.ext.azure.log_exporter import AzureLogHandler from opencensus.ext.azure.common import utils logger = logging.getLogger(__name__) logger.addHandler(AzureLogHandler( connection_string=os.environ['APPLICATIONINSIGHTS_CONNECTION_STRING'])) utils.azure_monitor_context['cloud.role'] = os.environ.get('WEBSITE_SITE_NAME', 'your-function-name')

Also ensure your requirements.txt includes:

opencensus opencensus-ext-azure opencensus-ext-logging opencensus-ext-requests

Set up Azure Monitor for your Python application

Once you have added this and restarted your Function App, you should see execution telemetry reflected consistently in the Azure portal's monitoring views.

Enable Azure Monitor OpenTelemetry for .NET, Node.js, Python, and Java applications

Please do not forget to “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.
Bathini Harshitha 5 Reputation points Microsoft External Staff Moderator

2025-06-02T09:36:46.05+00:00

Hi Cheah, Felix FC

We haven’t heard from you on the last response, and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, please respond with more details and we will try to help.
Cheah, Felix FC 20 Reputation points

2025-06-02T21:09:06.7+00:00

'WEBSITE_SITE_NAME', 'your-function-name' would these two be replaced with func-ttsiotdpp-nzs-prod and wise_data_dpp
Bathini Harshitha 5 Reputation points Microsoft External Staff Moderator

2025-06-03T03:27:16.3866667+00:00
Hi Cheah, Felix FC

Yes, you can replace 'your-function-name' with the name of your function (e.g: 'wise_data_dpp') and 'WEBSITE_SITE_NAME' will automatically resolve to the Function App name (func-ttsiotdpp-nzs-prod) at runtime, or you can just leave it as it is. That is only a backup value in case the environment variable is not set.

Use the below line:

utils.azure_monitor_context['cloud.role'] = os.environ.get('WEBSITE_SITE_NAME', 'your-function-name')

so, it will automatically work as expected if your WEBSITE_SITE_NAME is correctly set in the environment, which is usually done automatically by Azure.

Please do not forget to “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.
Cheah, Felix FC 20 Reputation points

2025-06-03T03:30:33.43+00:00

Website name doesn't seem to be in the environment variables
Bathini Harshitha 5 Reputation points Microsoft External Staff Moderator

2025-06-03T13:52:52.7166667+00:00

Hi Cheah, Felix FC

Thanks for checking that, from the Application Insights logs it is clear that your Function App is running in Azure App Service, which means WEBSITE_SITE_NAME should be automatically available at runtime. If you are not seeing it, it could be because you are checking from a local environment or using a custom container setup where Azure do not inject this variable by default.

Could you please confirm if you are using a custom container or testing this outside Azure?

Please do not forget to “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.
Bathini Harshitha 5 Reputation points Microsoft External Staff Moderator

2025-06-04T09:31:00.4933333+00:00

Hi Cheah, Felix FC

We haven’t heard from you on the last response, and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, please respond with more details and we will try to help.
Cheah, Felix FC 20 Reputation points

2025-06-09T21:39:44.1533333+00:00

Hi sorry havent had a chance to try this yet sorry
Cheah, Felix FC 20 Reputation points

2025-06-10T20:26:57.4633333+00:00

does this look right?
Cheah, Felix FC 20 Reputation points

2025-06-10T22:11:38.85+00:00

The function app doesnt seem to be running after the cahnges. is this bit suppose to be in the main code?
Cheah, Felix FC 20 Reputation points

2025-06-10T23:35:32.22+00:00

Result: Failure Exception: ModuleNotFoundError: No module named 'opencensus'. Cannot find module. Please check the requirements.txt file for the missing module. For more info, please refer the troubleshooting guide: https://aka.ms/functions-modulenotfound. Current sys.path: ['/home/site/wwwroot', '/home/site/wwwroot/.python_packages/lib/site-packages', '/azure-functions-host/workers/python/3.10/LINUX/X64', '/usr/local/lib/python310.zip', '/usr/local/lib/python3.10', '/usr/local/lib/python3.10/lib-dynload', '/usr/local/lib/python3.10/site-packages'] Stack: File "/azure-functions-host/workers/python/3.10/LINUX/X64/azure_functions_worker/dispatcher.py", line 546, in _handle__function_load_request func = loader.load_function( File "/azure-functions-host/workers/python/3.10/LINUX/X64/azure_functions_worker/utils/wrappers.py", line 49, in call raise extend_exception_message(e, message) File "/azure-functions-host/workers/python/3.10/LINUX/X64/azure_functions_worker/utils/wrappers.py", line 44, in call return func(*args, **kwargs) File "/azure-functions-host/workers/python/3.10/LINUX/X64/azure_functions_worker/loader.py", line 220, in load_function mod = importlib.import_module(fullmodname) File "/usr/local/lib/python3.10/importlib/init.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "/home/site/wwwroot/wise_data_dpp/init.py", line 8, in <module> from opencensus.ext.azure.log_exporter import AzureLogHandler

i get the error above
Cheah, Felix FC 20 Reputation points

2025-06-10T23:35:55.0733333+00:00

Result: Failure Exception: ModuleNotFoundError: No module named 'opencensus'. Cannot find module. Please check the requirements.txt file for the missing module. For more info, please refer the troubleshooting guide: https://aka.ms/functions-modulenotfound. Current sys.path: ['/home/site/wwwroot', '/home/site/wwwroot/.python_packages/lib/site-packages', '/azure-functions-host/workers/python/3.10/LINUX/X64', '/usr/local/lib/python310.zip', '/usr/local/lib/python3.10', '/usr/local/lib/python3.10/lib-dynload', '/usr/local/lib/python3.10/site-packages'] Stack: File "/azure-functions-host/workers/python/3.10/LINUX/X64/azure_functions_worker/dispatcher.py", line 546, in _handle__function_load_request func = loader.load_function( File "/azure-functions-host/workers/python/3.10/LINUX/X64/azure_functions_worker/utils/wrappers.py", line 49, in call raise extend_exception_message(e, message) File "/azure-functions-host/workers/python/3.10/LINUX/X64/azure_functions_worker/utils/wrappers.py", line 44, in call return func(*args, **kwargs) File "/azure-functions-host/workers/python/3.10/LINUX/X64/azure_functions_worker/loader.py", line 220, in load_function mod = importlib.import_module(fullmodname) File "/usr/local/lib/python3.10/importlib/init.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "/home/site/wwwroot/wise_data_dpp/init.py", line 8, in <module> from opencensus.ext.azure.log_exporter import AzureLogHandler

i get the error above
Cheah, Felix FC 20 Reputation points

2025-06-10T23:36:26.98+00:00

Result: Failure Exception: ModuleNotFoundError: No module named 'opencensus'. Cannot find module. Please check the requirements.txt file for the missing module. For more info, please refer the troubleshooting guide: https://aka.ms/functions-modulenotfound. Current sys.path: ['/home/site/wwwroot', '/home/site/wwwroot/.python_packages/lib/site-packages', '/azure-functions-host/workers/python/3.10/LINUX/X64', '/usr/local/lib/python310.zip', '/usr/local/lib/python3.10', '/usr/local/lib/python3.10/lib-dynload', '/usr/local/lib/python3.10/site-packages'] Stack: File "/azure-functions-host/workers/python/3.10/LINUX/X64/azure_functions_worker/dispatcher.py", line 546, in _handle__function_load_request func = loader.load_function( File "/azure-functions-host/workers/python/3.10/LINUX/X64/azure_functions_worker/utils/wrappers.py", line 49, in call raise extend_exception_message(e, message) File "/azure-functions-host/workers/python/3.10/LINUX/X64/azure_functions_worker/utils/wrappers.py", line 44, in call return func(*args, **kwargs) File "/azure-functions-host/workers/python/3.10/LINUX/X64/azure_functions_worker/loader.py", line 220, in load_function mod = importlib.import_module(fullmodname) File "/usr/local/lib/python3.10/importlib/init.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "/home/site/wwwroot/wise_data_dpp/init.py", line 8, in <module> from opencensus.ext.azure.log_exporter import AzureLogHandler

i get the error above
Cheah, Felix FC 20 Reputation points

2025-06-12T00:59:32.26+00:00

I got the function app working but the execution count is still zero, i can see the logs going into log analytics/app insights

nothing in invocations or metrics
Bathini Harshitha 5 Reputation points Microsoft External Staff Moderator

2025-06-20T16:37:34.18+00:00

Hi Cheah, Felix FC

If your Function Execution Count is showing zero, first ensure that your function trigger whether it is HTTP, Timer, Queue is correctly configured and actually being invoked.

Check your Application Insights logs to see if any executions are recorded there even if metrics aren't reflecting them yet. Also, verify the Metrics blade filter settings in Azure Portal Make sure the correct function name and time range are selected. It’s a good idea to restart the Function App in case there’s a deployment or runtime issue.

Finally, confirm any trigger-specific configurations such as a valid CRON expression for Timer triggers or a proper Storage Account connection for Queue triggers.

Azure Functions triggers and bindings concepts

Application Insights integration

Please do not forget to “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

Share via

Function App Function Execution Count at zero

1 answer

Your answer