We had 1 priority 1, 6 priority two's, and 1 priority 3's. All the two's were set to build if modifications existed as was the three, because one of the 2's would always kick off during a loop it would give the other two's time for their next modification check and they then jumped back into the queue ahead of the three. The end result of this was during normal business hours the #3 priority would almost never get its turn to check for modifications or respond to a force build from the web site. We had previously tried prioritizing from 1 to 8 but this also caused the same issue with the lower priority projects. There needs to be something in there to make sure all projects get checked or run once a loop, instead of allowing higher priorities to jump back in front of the lowers repeatedly.