Originally Posted by
no1cub17
Whew - we have this exact scenario coming up, surely that was a one-off with either a lazy/uninformed/uninspired agent. Needless to say we'll be allowing extra time at the airport that morning.
Yeah, AAgent error can always poke it's nose in.
In this case, you can print out the policy from AA in case they "confuse" the Oct 15 change to include connections to/from OneWorld. (as opposed to the many policies where there's no way of doing that.)