Azure function app time trigger function execution issue

[Saranya770]

It's working as expected, but the problem is that sometimes it silently fails. It doesn't execute the entire process; instead, it stops abruptly in the middle. I'm getting this log message:
"Stopping the listener Microsoft.Azure.WebJobs.Host.Listeners.SingletonListener for function."

Are there any ways to resolve this?

Code: Python

[nturinski]

Timer triggers run as singletons using a blob lease (the “host lock”) to guarantee only one instance runs at a time. If the lease can’t be acquired (or the host enters drain/stop), the platform stops the listener, and you’ll see that message.

In scaled-out apps or during host restarts/updates, the listener will periodically try to reacquire the lock; if it cannot, executions won’t fire and it can look “silent.”

If you use the same storage account for multiple Function Apps (or slots) with identical function names, they can compete for the lease and suppress each other. Maybe try using separate storage or distinct names?

On Consumption and Flex Consumption, cold start or worker startup timeouts can mask listener start problems; on a dedicated App Service plan, you must enable Always On to keep the host alive.