Hello,
I faced the issue today, back from the week-end my Azure WebJobs deployed last friday had the status Aborted.
After some research, I found that the running time of my webjob was more than 20 minutes.
20 minutes is the average time of the Azure WebApp time out, this time out has the effect to stop (aborted) the Azure WebJob.
But then how to solve it, if you want to have an Azure WebJob running much longer ?
- Go to your Azure portal
https://portal.azure.com
- Find and open your Azure WebApp panel
- Select the “settings” menu as showed in the picture below
- Then in the new menu that just pop out, select the “Application settings”. There you will find the property “Always On”. This is the key to keep your job running.
The picture below show you the menu
I’m my case you see that the option is not clickable. This is because I’m using a Free web app pricing plan.
Loïc Sterckx - Office 365 & Azure PaaS 
it does not work, the process was cut after 28 minutes
LikeLike
Hello Hanz,
Please find here a print screen of a WebJob running on my own tenant with 3 hours of execution time.
Can you maybe share your settings of your WebApps ?
Loic
LikeLike
I was looking for solutions to my problem, because with the “Allways On” was not enough. And I found that you can also set parameters with keys to control the time of Aborted. Here is the link as a contribution to those who need it:
https://github.com/projectkudu/kudu/wiki/Web-jobs#configuration-settings
use “WEBJOBS_IDLE_TIMEOUT” for webjob timeout.
I hope it will help, thanks.
LikeLike
Hello thanks for your comment.
I saw in the post:
“WEBJOBS_IDLE_TIMEOUT – Time in seconds after which we’ll abort a running triggered job’s process if it’s in idle, has no cpu time or output (Only for triggered jobs).”
So this is more to cut a webjob when it is waiting for something. It was something like that on your side ?
I still do have jobs running for hours without changing this property.
Thanks.
LikeLike