rule sending to wrong pool if connection is already established

Thanks Aaron. I verified that works. We already are using oneconnect in production but not QA where we discovered this. I also like the idea of an explicit else statement and will play with the best way to approach it.