Timer Trigger Azure Function App not firing on hourly schedule

Marcellus Davenport 0 Reputation points Microsoft Employee
2024-04-06T15:55:33.15+00:00

Problem: Deployed Azure Function app is not firing on hourly CHRON schedule I have configured.

What I've done

  • Verified my CHRON expression is correct for hourly schedule ("0 0 * * * *")
  • Verified function works by manually triggering via Code+Test section in the portal
  • Set WEBSITE_TIME_ZONE environment variable to "Pacific Standard Time"

Note: I'm using Premium app service plan so I don't have the options to set "Always On" configuration setting

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,389 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. MayankBargali-MSFT 69,581 Reputation points
    2024-04-08T06:21:30.1433333+00:00

    @Marcellus Davenport Thanks for reaching out.

    Your CORN expression looks good (0 0 * * * *) and it should trigger your function every hour.

    Have you review Diagnose and solve problems blade on your function app for the detector "Timer Trigger Incomplete Execution Detection" and "Timer Trigger Issue Analysis" to get more insights on the issue why your timer trigger was not triggered. I will also suggest to validate if there are any run time errors on your function using the diagnose blade or application insights logs to get more insights on the issue.

    The most common cause for Azure Functions not getting triggered is that triggers are not synced properly. You can sync triggers as documented here.

    In case if you are still not able to find the insights on figure out the issue then please let me know.


  2. Pinaki Ghatak 2,405 Reputation points Microsoft Employee
    2024-05-13T09:15:50.4433333+00:00

    Hello @Marcellus Davenport

    Since you are using a Premium app service plan, you do not have the option to set the Always On configuration setting. One thing to note is that the timer trigger for Azure Functions uses a storage lock to ensure that there is only one timer instance when a function app scales out to multiple instances.

    If two function apps share the same identifying configuration and each uses a timer trigger, only one timer runs. Additionally, the timer trigger does not retry after a function fails. When a function fails, it isn't called again until the next time on the schedule.

    If you have ruled out all of the above possibilities, it's possible that there may be an issue with the Azure Function app itself. In this case, I would recommend checking the Azure Functions logs for any errors or warnings that may be preventing the function from running on schedule. You can also set up monitoring and alerting for Azure Functions by using Azure Application Insights.

    I hope this helps


    I hope that this response has addressed your query and helped you overcome your challenges. If so, please mark this response as Answered. This will not only acknowledge our efforts, but also assist other community members who may be looking for similar solutions.

    0 comments No comments