All of the above flights are actually non-stop. However, for some reason, the [Enhanced Seat Maps] Engine currently sees them as being UA-coded only, which, in turn, causes the error.
Odd, must be a recent change. I've checked these within the last few days. Maybe an effect of the merger?
Ohh, and I had trimmed out the connecting flights which is why they were all non-stop
The query brings back connecting flights as well.
I also ran into something on another query with seat maps, maybe related? It was telling me that a certain cabin didn't exist on the flight. It was a CO flight and I was checking for business (which used to work). However it would let me bring up F which would be more typical of UA.