| My expectation of selecting 'Stop/Disconnect on Idle Timeout' and setting a Maximum Total Uses value of, say, 10, would be that after running 5 jobs, the instance being stopped due to idle timeout, then 5 more jobs running on that instance, the instance would be terminated and the next job would launch on a new instance. What I am seeing is that after running 5 jobs and the Maximum Total Uses number dropping to 5, after the agent instance stops, and is then started again, the Maximum Total Uses remaining number resets itself to 10. The same instance has been used 5 times but that information is lost. Is this behaviour expected? If not, would a pull request be accepted or a fix be available to maintain the number of uses remaining across starting and stopping of an instance? Many thanks |
