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(9.6, 49%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDD%3C/text%3E%3C/svg%3E)
I've read that the "proper" (debatable) way to stop a scheduled webjob is to get to scm and delete the settings.job file. However, my project is deployed as a zip through devops so I can't delete files. Trying gives 409.
I also can't delete the job. Portal tells me it's deleted, but it's not.
I've tried stopping the app service but the jobs keep running. What are the other options?
![](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(256, 10%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EX%3C/text%3E%3C/svg%3E)
Adding an Application settings value of WEBJOB_STOPPED with a value of 1 to stop the job. Here is a reference article for webjobs, https://dori-uw-1.kuma-moon.com/en-us/azure/app-service/webjobs-create
Hope this helps and don't forget to mark answer if it helped you!
![](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(147.20000000000002, 55.00000000000001%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
@Deanna Delapasse , Just checking in to see if the above post helped answer your question. Kindly let us know if you have any further questions on this specific topic, we would be more than happy to assist you.
Please do mark the post which was helpful by clicking on ‘Accept Answer’ & ‘Up-Vote’ to help the community find the right answers.
@xequence @Anonymous It doesn't seem modifying the portal app settings during a run effects the running process. I also tried setting WEBJOBS_DISABLE_SCHEDULE but that one didn't help either.
I have one app service with 3 webjobs (1 continuous and 2 triggered).
![](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(313.6, 90%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
I believe the WEBJOBS_STOPPED and WEBJOBS_DISABLE_SCHEDULE only work in non-production deployment slots.
You can access the settings.job file via azure portal, in the developer side menu option 'App Service editor(preview)' where your file is under app_data/Jobs/Triggered/yourwebjobappnamehere/Settings.job
and maybe change it from
{
// Runs at 3:00 AM every week day
"schedule": "0 0 3 * * 1-5"
}
to
{ // Runs at 3:00 AM every week day
"disabled": true,
"schedule": "0 0 3 * * 1-5"
}