Menu
We've deployed an on demand Azure webjob and it is in an endless loop. We figured out the bug, did a redeploy and that failed. So we deleted the old job and went to deploy it again but now the job won't start. There is a file called triggeredJob.lock that I've tried to delete but it is in use and I believe that is what's causing the conflict.
Is there a way to recycle the whole app to get this to stop and release the files?
830
Two solutions:
The simplest is to just hit the Restart button in the Azure portal for the Web App that hosts your WebJob, giving a clean start to all processes.
The more complex but less heavy weight is to go to your Web App's Kudu Console. From there, click on the Process Explorer tab. Find the relevant WebJob process in the list, right click it and choose Kill.
160
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
