I know it sounds crazy, but it really is working as designed. If for example you've got the value set to 50 then you should be able to have 50 sessions running in the pool during the recompose, the fact that 30 of them are already connected before you start is unrelated. What you're looking for is a feature that always preserve the pool headroom value during a recompose, so that a recompose will not happen if it's expected to violate the headroom count - this is slightly different, would be very useful but sadly doesn't exist today.
↧