azure function app to view timer trigger status

Question

azure function app to view timer trigger status

TAH 40

Hi all,

i would like to ask if anyone know about azure function app service

type: container

lanaguage: python

how do i view function app under the overview, function trigger scheduled status eg last run and next run status

when i view the code+test, the log shown as you are connected but it is blank. is there other way to view the function app timer trigger app.py status log

0 comments

Answer accepted by question author

Rakesh Mishra 11,340 Microsoft External Staff Moderator

Hi @TAH ,

Welcome to Microsoft Q&A portal. Thank you for posting your question here.

This is a common behavior when working with Azure Functions running in a Linux Container with Python. Below is an explanation of why you are experiencing this and the official, reliable methods to check your timer schedule status (last/next run) and view your application logs.

1. How to View Timer Trigger Scheduled Status (Last Run & Next Run)

In Azure Functions, the general Overview blade of the Function App does not natively display a live countdown or "Next Run" schedule widget for containerized functions. However, the Functions runtime natively persists this schedule state in Azure Storage. Check the Function's Monitor Blade (Last Run & History)

In your Function App, go to Functions --> select your specific Timer Trigger function --> click Monitor.
Under the Invocations tab, you will see the historical log of Last Run execution timestamps, success/failed status, and execution duration.

2. Why "Code + Test" Logs are Blank (Even When "Connected")

When running a Python Function App inside a Custom Container, seeing a blank console in the Code + Test blade is expected due to the following reasons:

Container I/O Routing: The lightweight log streamer used in the Code + Test blade is primarily designed for standard in-process hosting. For Linux container deployments, standard console output (stdout/stderr) emitted from inside the isolated Docker container is often not routed to this ephemeral portal UI session.
Asynchronous Timer Intervals: Live log streaming only displays events that occur while your browser is actively connected to the stream. Because timer triggers execute on a schedule (e.g., once an hour or once a day), the console will remain completely blank unless the timer happens to trigger during the exact window you are watching the screen.
Python Logging Setup: Ensure your app.py is utilizing the standard Python logging module (e.g., logging.info("Timer triggered")) rather than standard print() statements, as print() calls are not guaranteed to flush to Azure telemetry buffers without unbuffered I/O enabled.

3. Reliable Ways to View Python Container Logs & Timer Status

Option 1: Application Insights (Recommended Official Approach)

For container-based deployments, Application Insights is the most robust way to view historical logs, traces, and upcoming schedule evaluations.

In your Function App, go to Monitoring --> Logs (Log Analytics).
Run the following KQL queries to check execution history and schedule announcements:

// View historical timer executions and status
requests 
| where name contains "<YourTimerFunctionName>" 
| order by timestamp desc

// View your app.py logging.info() outputs and host schedule announcements
traces 
| where message contains "<YourTimerFunctionName>" or message contains "Next schedule for function"
| order by timestamp desc

Option 2: App Service / Container Log Stream

Navigate to your Function App --> under Monitoring, click Log stream (or check Deployment Center -->Logs).
This stream captures platform-level Docker container logs and Functions host startup events. You can observe the container initialization sequence here to confirm whether your Python timer trigger was indexed and scheduled successfully upon startup.

References:

https://learn.microsoft.com/en-us/azure/azure-functions/analyze-telemetry-data

0 comments

1 additional answer

Your answer

Answer 1

For a timer-triggered Azure Function, the most reliable ways to verify execution are logs and monitoring data.

In the Azure portal, open the function app and use Log stream to watch executions in real time. A running timer trigger should write entries according to its schedule.
In the function, open Code + Test and expand Logs. If it shows connected but stays blank, that usually means no log entries are being emitted there.
If Application Insights is enabled, use it to review historical execution data and traces. Historical logs can be queried from Application Insights, including request and trace data.
For complete execution logs, enable Diagnostic settings and query the FunctionAppsLogs table.
For timer triggers specifically, execution visibility depends on logs. Timer-triggered functions do not retry after a failure; they run again only at the next scheduled time.
Timer triggers also depend on the host storage connection (AzureWebJobsStorage). The runtime uses blob storage coordination for timer execution.

If the goal is to confirm whether the timer is firing:

Open the function app in the Azure portal.
Select Log stream and wait for the next scheduled interval.
Check whether log entries appear for the timer execution.
If no entries appear, review Application Insights traces and diagnostic logs.
If running locally, start the Functions host with func start; the host writes timer-triggered execution information to the terminal.

If the schedule is defined in a Python v1 timer trigger, the schedule is set in function.json by the schedule property. Example:

{
  "schedule": "0 */5 * * * *",
  "name": "myTimer",
  "type": "timerTrigger",
  "direction": "in"
}

Important timer-trigger details:

runOnStartup should be used with caution and rarely in production.
useMonitor is true by default for schedules with recurrence intervals of 1 minute or more.
If two function apps share the same identifying configuration and both use a timer trigger, only one timer runs.

For deeper monitoring in Azure, metrics are available under Monitoring > Metrics, and Application Insights can be used to analyze failures, exceptions, and execution behavior.