It looks like the recent updates have left variable handling in a bad state. When I have two variables with the same name, and one of them is checked, there are times where Postman picks the one that’s unchecked. The UI changes are confusing too. It’s not obvious what is checked unless you hover over it. I’ve seen some other issues as well, and it’s turning this tool into something that is hard to use. Is there a timetable for resolving these bugs?
Hey @jlarge 
Welcome to the Postman Community! 
Would you be able to share some examples of where you are seeing those issues please?
When you have 2 variables with the same name, in the same scope, there is a visual indicator informing you that one will be overwritten.
If you happen to have more than 2 with the same name, they would both be overwritten.
When a variable is not selected the row colour is changed and the warning indicator is also removed, as the variable will not be used.
The variables in request section, would give you the value of what is being used in the request.
If you also wanted to share some of the other issues that you have been seeing, I’d be happy to take a look and if required, raise those up to the dev team to take a look 
I can’t seem to reproduce this now, but when it was happening, I had two collection variables named api-management.host, each with different values. There were times when I’d check the first one and uncheck the second one, but when I ran a request, it would use the unchecked one. Also, the new interface doesn’t show whether things are checked unless you hover over it. Without hovering, you just have inactive rows that are slightly greyer than other rows, so it’s not as readable as it used to be.