Cloud profiles not starting new agents if pre-existing disabled instance exists

Hi,

I'm currently using TeamCity 2017.1.5. I'm encountering a situation in which I have a cloud profile in a pool, with an instance of that cloud profile already started (and idle) but disabled. In this case, a build assigned to that pool appears to wait indefinitely-- based on an earlier post (https://teamcity-support.jetbrains.com/hc/en-us/community/posts/206048219-Detailed-explanation-of-cloud-agents-allocation-strategy-and-license-usage-) I'd assume the agent was recognized as 'available', so the cloud profile doesn't start another agent, but the existing agent in that pool won't actually pick up the waiting build (because it's disabled). Is this the case? If so, is there any way to have the cloud plugin recognize that it needs to start a new agent in this situation?