Originally Posted by
goodeats21
I find it hard to believe that having a Lowest Fare moniker with "unavailable" is designed behavior.
If there is any fare available, there has to be a lowest fare available, no?
I don't think it's a good UX choice, but I do believe that whoever wrote the code did intend it work that way (i.e. it's not a bug in OP's particular case).