Timer Functions stopped triggering as of 11/23

Question

Timer Functions stopped triggering as of 11/23

Forgelight 0

Having a weird problem as of late where my timer functions on one of my function apps stopped running on 11/23/2025 - this is weird because all of my other timer functions on my other function apps are still working as they should.

The function app in question User's image

The function used to run every hour without incident for months, but all of a sudden it stopped working - the function hasn't been touched nor edited since setting it up

User's image

Cron expression

User's image

Same situation with another timer function I have on this function app - stopped running on 11/23/2025, any help would be greatly appreciated as I have no idea what's happening

Rakesh Mishra 4,880 Reputation points Microsoft External Staff Moderator

2025-12-03T12:53:56.4+00:00

Hi @Forgelight ,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

We have checked on the backend and the function CamaignRunTimeCheck is executing every hour. The issue might happen due to

Restart of function at the time of invocation

It is recommended to enable AlwaysOn. If the Azure Functions app is inactive for an extended period of time, the process associated with it is shut down to conserve resources. Subsequent requests following a long idle time, may take longer to respond as the process has to be re-started and the site re-initialized.
Josh Sutherland 0 Reputation points

2025-12-30T12:00:15.63+00:00

Where and how do I enable "AlwaysOn?" I didn't do anything to the function other than troubleshooting with the support team and it just started working again
Rakesh Mishra 4,880 Reputation points Microsoft External Staff Moderator

2026-01-06T23:19:18.03+00:00

Hi @Forgelight , I hope you checked my last response, and it was helpful. Please do let me know if you need any further assistance on this.
Rakesh Mishra 4,880 Reputation points Microsoft External Staff Moderator

2026-01-06T23:23:45.7+00:00
Hi @Josh Sutherland , could you please confirm if issue is resolved now.

Regarding Enabling AlwaysOn in Azure Portal,

Sign in to the Azure portal and open the Function App.

In the left menu choose Configuration → General settings.

In General settings toggle Always On → On and Save.

Note: Always On is only available / required when your Function App runs on a dedicated App Service (App Service) plan (Basic/Standard/etc.). If your app is on the Consumption plan the platform automatically activates instances and you normally don’t need this setting; if it’s on Free/Shared the toggle won’t be available — you must scale up to Basic or higher to see it.
Josh Sutherland 0 Reputation points

2026-01-07T12:07:36.7833333+00:00

Hey Rakesh, there is no Always On option
Praveen Kumar Gudipudi 1,505 Reputation points Microsoft External Staff Moderator

2026-01-09T05:45:00.01+00:00
Hello @Forgelight ,

Could you please verify below details and provide confirmation to proceed further:

If storage becomes unreachable or misconfigured, timers silently stop so please check AzureWebJobsStorage connection string and connectivity between storage account and function app.

This is a KNOWN ISSUE (not your code) To fix the issue please restart the function app.

If you still facing same issue, please provide application logs over private message.
Praveen Kumar Gudipudi 1,505 Reputation points Microsoft External Staff Moderator

2026-01-12T04:32:56.2833333+00:00

Hello @Forgelight ,

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, will respond with more details and we will try to help.
Josh Sutherland 0 Reputation points

2026-01-12T12:11:43.98+00:00

@Praveen Kumar Praveen It just started working again - I didn't do anything but I received this response from support:

"The logs were reviewed to identify the reason scaling had stopped for a Function App. It was found that log-related performance metrics on the Scale Controller had dropped significantly, suggesting that a Scale Controller instance entered a bad state on November 23rd and stopped monitoring events. This problem affected several clients globally. The issue was resolved by restarting the impacted FrontEnd (FE) role."

1 answer

Your answer

Rakesh Mishra 4,880 Reputation points Microsoft External Staff Moderator

2025-12-03T12:53:56.4+00:00

Hi @Forgelight ,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

We have checked on the backend and the function CamaignRunTimeCheck is executing every hour. The issue might happen due to

Restart of function at the time of invocation

It is recommended to enable AlwaysOn. If the Azure Functions app is inactive for an extended period of time, the process associated with it is shut down to conserve resources. Subsequent requests following a long idle time, may take longer to respond as the process has to be re-started and the site re-initialized.
Josh Sutherland 0 Reputation points

2025-12-30T12:00:15.63+00:00

Where and how do I enable "AlwaysOn?" I didn't do anything to the function other than troubleshooting with the support team and it just started working again
Rakesh Mishra 4,880 Reputation points Microsoft External Staff Moderator

2026-01-06T23:19:18.03+00:00

Hi @Forgelight , I hope you checked my last response, and it was helpful. Please do let me know if you need any further assistance on this.
Rakesh Mishra 4,880 Reputation points Microsoft External Staff Moderator

2026-01-06T23:23:45.7+00:00

Hi @Josh Sutherland , could you please confirm if issue is resolved now.

Regarding Enabling AlwaysOn in Azure Portal,

Sign in to the Azure portal and open the Function App.

In the left menu choose Configuration → General settings.

In General settings toggle Always On → On and Save.

Note: Always On is only available / required when your Function App runs on a dedicated App Service (App Service) plan (Basic/Standard/etc.). If your app is on the Consumption plan the platform automatically activates instances and you normally don’t need this setting; if it’s on Free/Shared the toggle won’t be available — you must scale up to Basic or higher to see it.
Josh Sutherland 0 Reputation points

2026-01-07T12:07:36.7833333+00:00

Hey Rakesh, there is no Always On option
Praveen Kumar Gudipudi 1,505 Reputation points Microsoft External Staff Moderator

2026-01-09T05:45:00.01+00:00

Hello @Forgelight ,

Could you please verify below details and provide confirmation to proceed further:

If storage becomes unreachable or misconfigured, timers silently stop so please check AzureWebJobsStorage connection string and connectivity between storage account and function app.

This is a KNOWN ISSUE (not your code) To fix the issue please restart the function app.

If you still facing same issue, please provide application logs over private message.
Praveen Kumar Gudipudi 1,505 Reputation points Microsoft External Staff Moderator

2026-01-12T04:32:56.2833333+00:00

Hello @Forgelight ,

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, will respond with more details and we will try to help.
Josh Sutherland 0 Reputation points

2026-01-12T12:11:43.98+00:00

@Praveen Kumar Praveen It just started working again - I didn't do anything but I received this response from support:

"The logs were reviewed to identify the reason scaling had stopped for a Function App. It was found that log-related performance metrics on the Scale Controller had dropped significantly, suggesting that a Scale Controller instance entered a bad state on November 23rd and stopped monitoring events. This problem affected several clients globally. The issue was resolved by restarting the impacted FrontEnd (FE) role."

Answer 1

Hello Josh Sutherland,

Thanks for sharing the details,

Issue: Timer Functions stopped triggering as of 11/23.

Resolution: The logs were reviewed to identify the reason scaling had stopped for a Function App. It was found that log-related performance metrics on the Scale Controller had dropped significantly, suggesting that a Scale Controller instance entered a bad state on November 23rd and stopped monitoring events. This problem affected several clients globally. The issue was resolved by restarting the impacted FrontEnd (FE) role.

Please accept as answer and do a Thumbs-up to upvote this response. Your upvote will be beneficial for the community users facing similar issues.

Share via

Timer Functions stopped triggering as of 11/23

1 answer

Your answer