Function with daily timer trigger suddenly stopped

Chris Ahrens 0 Reputation points
2025-08-08T13:56:18.8766667+00:00

I have a Function App, with numerous Timer triggered functions. They all have been working without issue, but today I noticed that one of the daily functions has not run since 7/24. No errors, and it's still listed as enabled.

I found a help article and suggested I post this here, along with the following questions.

  1. Are you using Consumption or App Service Plan - App Service Plan
  2. If Consumption, how did you deploy? If App Service Plan, do you have Always On enabled? - NA
  3. Are you using the v1 runtime, or the v2 (Preview) runtime? - v4... I think?
  4. Are you setting WEBSITE_TIME_ZONE? - Not sure
  5. What is your CRON expression set to, and what is your expectation about what it means. e.g. state "I expect it to fire every thursday at 14:17". In some cases, users just misunderstand the CRON syntax, and have incorrect expectations about the semantics of a particular expression. *- [TimerTrigger("0 10 * * ")] I expect this to run daily at 10am UTC
  6. Give a specific UTC time at which you expected your function to get called, and found that it wasn't. Also, explain how you are determining that it is not getting called. If some cases, the function may get called, but it may not be obvious due to some logging issue. - Every day since 7/24 at 10 AM UTC. There is no history beyond 7/24 in the invocations history table. Also, the output of this function would be some changes to my DB and there are none.
  7. And most importantly, include a sample invocation ID so we can find your app and look into the issue. Follow these instructions to see how to share this. - e0e0b0b0a6f4228079a5f82fcc3b649f is the operationId of the last run
Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Chris Ahrens 0 Reputation points
    2025-08-08T19:19:05.7333333+00:00

    I found the issue in application insights. I had an out of memory exception. Once that was addressed it worked again. Though, I'm not sure why it showed as never running at all for the past 15 days in the invocations history... that was a bit deceiving. Also would have been a nice place to see the error, would have saved me a few hours.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.