Overview
Have you published a long running web job in Azure and noticed that it has terminated with an ‘Aborted’ status. Chances are that the job has timed out.
In this post I’ll explain what’s happening here and how you can fix this.
So What’s Going On?
WebJobs run within the context of the parent websites IIS worker process. When the website shuts down, guess what, so does your WebJob!
Microsoft states that Web Jobs running on the Free Tier will timeout after 20 minutes of inactivity, unless you set them to be Always On.
How do I fix it?
If you’ve got a long running process running within your WebJob you’ll need to enable the Always On mode to ensure your WebJob doesn’t get killed after 20 minutes of inactivity of your website hosting your WebJob.
1. Log into the Azure Portal – https://portal.azure.com
2. Open the App Service that your WebJob is running within.
3. Open the APPLICATION SERVICES panel
4. Enable the ALWAYS ON option
Having Trouble?
If the ALWAYS ON option isn’t enabled for you, chances are that you’re probably on the Free Tier.
You’ll need to upgrade to at least a Basic plan before you can access this feature.
This blog is my place to share my thoughts, helpful solutions and just random nerdy stuff.
- Solved: Build Errors Not Showning in VS 2022 - 21st November 2024
- How To: Configure VSCode to Trust Self-Signed Certs - 16th August 2024
- Solved: GitHub Actions – HTTP 403: Resource not accessible by integration - 13th June 2024
11th July 2019 at 1:51 pm
Hello, I had the same error message when I was scaling down the App service plan tier. The error was due to file storage does not enough to store in the low tier since the low tier had only 1GB but my file directory was bit more. I deleted the unwanted files in azure app service and republished my service and then changed it to low tier. It worked!!! Hope this was useful. Thanks