![]() |
Phantom Record Locator/Flight???
on both the App and the website, I have an orphan record locator/flight that I can't open or access. The record locator was for a RT that I did last month that should have completed the itinerary. On the website, it still exists but if I open it I get an error. On the app, the record locator indicates a flight in early March but the app can't open it.
It will probably resolve but I can't delete it or anything. Anyone else ever see this behavior? |
Did you try contacting AA?
|
Originally Posted by fliesdelta
(Post 36005730)
Did you try contacting AA?
|
Originally Posted by JMN57
(Post 36007352)
No - trying to converse with AA is, IMO, asking for frustration. The "problem" doesn't present any issues and I expect it will resolve on its own when the date (March 6) of the entry arrives. Just odd behavior and I was curious if anyone else had experienced same.
|
Originally Posted by fliesdelta
(Post 36008184)
I never had this happen so I never contacted AA for this kind of thing, but lately I've had some good chat experiences with them, including the week before last when I was flying SFO-DFW-RDU and the SFO-DFW leg was running late and at one point my connection time was down to about 18 minutes. Via chat I got protected on the first flight the next morning (I was on the last DFW-RDU). Fortunately the connection ended up being about 25 minutes and I made it to my DFW-RDU seat with a few minutes to spare.
|
| All times are GMT -6. The time now is 3:05 pm. |
This site is owned, operated, and maintained by MH Sub I, LLC dba Internet Brands. Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Designated trademarks are the property of their respective owners.