Azure Web Job - Scale out kills existing web job
<p>I'm looking to use the API to change the number of web job instances I have running based on the size of a processing Q, I know I can setup rules in the portal but the minimum aggregation time is 60 minutes and I don't want to have the system waiting 60 minutes before scaling up if we suddenly get a burst of work.</p>

<p>The issue I have is that currently if I scale out in the portal manually from say 1 to 5 instances it kills the single running instance and then starts 5 new ones.</p>

<p>I assume if I did this through the API the same thing would happen, do you know if there is any way to avoid this?</p>

<p>Thanks</p>

<p>Si</p>

<p><strong>UPDATE</strong>:
 See below, I submitted 4 jobs and then as the first was processing I scaled out from 1 to 3 instances and this is what happened, the job that Never Finished then reran after the next 3 had finished as it's message would have popped back on the queue because it's processing failed initially.</p>

<p><a href="https://i.stack.imgur.com/8c3GF.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/8c3GF.png" alt="enter image description here"></a></p>