locked
WebJobs issues : Timeout and Conflict RRS feed

  • Question

  • Hello,

    This morning , I have had two problems with my WebJobs. Here is the report obtained from Scheduler :

    1) Http Action - Request to host 'mywebjob1.scm.azurewebsites.net' failed: The timeout (30 seconds) was reached.
     
    2) Http Action - Response from host 'mywebjob2.scm.azurewebsites.net': 'Conflict' Response Headers: Pragma: no-cache
     x-ms-request-id: d9dbb40b-655e-4b99-a057-d7524a7796c6
     Cache-Control: no-cache
     Date: Tue, 24 Nov 2015 10:00:14 GMT
     Set-Cookie: ARRAffinity=40258b45cb7121dc481a90b62ca13f19fda0fb98192a595db93c72ef98635e7e;Path=/;Domain=mywebjob2.scm.azurewebsites.net
     Server: Microsoft-IIS/8.0
     X-AspNet-Version: 4.0.30319
     X-Powered-By: ASP.NET
     Body: Cannot start a new run since job is already running.
     
     
     Any help appreciated.

    Thanks
    Tuesday, November 24, 2015 2:09 PM

All replies

  • Hello

    I have the same issue since 3 days. The scheduled webjobs can not be started manually and automatically.

    The error in the web job history is:

    Http Action - Response from host 'myservice.scm.azurewebsites.net': 'Conflict' Response Headers: Pragma: no-cache x-ms-request-id: ec0ef74e-37bb-4a74-b3bb-24be00c87f92 Cache-Control: no-cache Date: Mon, 13 Feb 2017 22:54:30 GMT Set-Cookie: ARRAffinity=b9c66f4aa579c732a5808715a1ad027a61bf5059793475606d99f9f10bab31e1;Path=/;Domain=myservice.scm.azurewebsites.net Server: Microsoft-IIS/8.0 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET Body: Cannot start a new run since job is already running.

    The body message "Cannot start a new run since job is already running" is absolutely incorrect, because I deleted the job before.

    Has Azure WebApp-Team any idea what's happened?

    Thanks Tino


    TM

    Monday, February 13, 2017 11:00 PM