This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 39%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDT%3C/text%3E%3C/svg%3E)
I was trying to deploy two function apps using one arm template arm_template: twoFunc_deployment.txt. Now the two function apps are getting deployed correctly but the expected behavior that it must start execution automatically as per the given trigger that is '0 */3 * * * *' so it must execute every 3 minutes, but that is not happening. But once I open the function app in the portal then the function app starts executing as per the given interval.
Assuming an issue with the approach, I deployed a Single Azure Function App which has only one timer trigger function which is supposed to run at an interval of every 3 minutes, arm_template: single_deployment.txt. Now after the deployment the function app is not starting any form of execution. I deployed the function app at 11:20 am IST and waited for 20 minutes then opened the function app on the portal. Now actual behavior should have been that there would be around 5-6 executions but there were none. Then when checked into the traces, it shows the logs starting from 11:41 am IST which is the time at which I opened the function app in the portal. This shows that the function app is only starting execution once I open it in the portal. Please someone help me regarding this issue.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 4%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Can we please check if your function app is in consumption plan it might be facing cold start.
Yes, my function app is in consumption plan.
This is an expected behaviour to keep the timer trigger running you need to either move to elastic premium plan or keep the azure function awake by writing custom apis https://microsoft.github.io/AzureTipsAndTricks/blog/tip260.html
Following up to see if the answer below clears things up. Feel free to get back to us if you need any assistance.
Please 'Accept Answer' if it helped so that it can help others in the community looking for help on similar topics.
This is expected behaviour either you can move to elastic premium plan or keep your function app alive by writing some custom api which keep hitting the function app https://microsoft.github.io/AzureTipsAndTricks/blog/tip260.html
Okay but what is the reasoning behind it starting invocation once I just visit that azure function's page on portal
After your function app has been idle for a number of minutes, the platform may scale the number of instances on which your app runs down to zero. The next request has the added latency of scaling from zero to one. This latency is referred to as a cold start. The number of dependencies required by your function app can affect the cold start time. Cold start is more of an issue for synchronous operations, such as HTTP triggers that must return a response. If cold starts are impacting your functions, consider running in a Premium plan or in a Dedicated plan with the Always on setting enabled. https://learn.microsoft.com/en-us/azure/azure-functions/event-driven-scaling?tabs=azure-cli#cold-start
Once you go to the portal the function app again gets warmed up so the invocation again starts