Robin Shen [24/Dec/11 05:26 AM] I checked the code, and the #available is impossible to be "-1". We will round it to 0 if the value is less than 0. If you still encounter this, please let us know the reproducing step. However it is possible that a resource with only 1 count can display a usage count of 2. Considering this case: 1. define a resource "db" with only one account at some agent. 2. master step of configuration "root/A" requires resource "db" to run, and it triggers and waits for finish of "roo/B". 3. master step of configuration "root/B" requires resource "db" to run, and it simply sleeps for some time. In this case, master step of "root/B" is permitted to run as otherwise a deadlock will occur. Also allowing resource "db" to be occupied by master step of "root/B" will not cause problem as "root/A" is waiting and the acquired resource "db" is actually not being used. However in this case, QB can not distinguish whether or not the resource is used by which configuration, it simply displays all steps acquired the resource. This also holds true in case when one configuration triggers and wait for another via the QuickBuild repository. If this is not your case, please let us know the reproducing steps.