Originally Posted by
anteater
FYI - removing and re-adding a FF# does not trigger a status update on the reservation. This action has no link to any specific back-end action. It has no affect, contrary to some of the anecdotal reports posted.
That seems hard to believe, as the original time you'd add a non-AS FF to a booking would definitely trigger a OW status lookup. I don't understand why re-applying an FF number (after removing it) would not trigger the same lookup.
I don't see a good reason to somehow cache status instead of doing a new lookup (assuming there is indeed a lookup, as opposed to a periodical download of every OW FF number and status which would then be stored in an AS database). No idea how this is implemented so it's just an educated guess on what would be a logical way to implement it.