I’m not sure the best way to file this bug report, so I’ll post it here to see if it’s more widespread.

On the Beta site, it says we should be able to make route based flight availability alerts. The help documentation states that we do this by leaving out the optional flight number, and then “any non-stop or direct flight for that day can trigger the alert.” This seems like exactly what I want.

Unfortunately, it keeps triggering for me, even with connecting flights.

I’ve had the following flights trigger my alerts incorrectly:

- LX 450 (ZRH -> LCY) triggered an alert searching for space in “I” from ZRH to BOS on 4/25/22. It seems to think I could connect onward to UA 25 from LHR -> BOS on 4/26/22, but this is obviously not a direct or a non-stop flight. The alert only mentions LX 450; I had to work out the possible UA 25 connection on my own by repeating the Award & Upgrade search by hand.
- LX 316 (ZRH -> LHR) triggered an alert searching for space in “I” from ZRH to BOS on 5/23/22. Again, I’m guessing it seems to think I could connect on UA 25 LHR -> BOS on 5/24/22.