unable to book on dl.com
Mar 31, 2009, 9:36 pm
#1
Original Poster
Join Date: Nov 2007
Programs: Delta GM, Hyatt Plat.
Posts: 91
unable to book on dl.com
Anyone else getting the ::::Your booking session has expired. Please start over. :::: error? am I doing something wrong?
Apr 1, 2009, 9:05 am
#3
Join Date: Jan 2008
Location: KATL
Programs: DL DM/2MM
Posts: 2,034
Yes, I'm getting the same error msg. And unfortunately, no, logging out and back in doesn't fix it.
Doing the chat thing now to see if I can find an answer.
Answer from online chat: Search by Schedule works. But the normal Search or Search by Price doesn't.
I can't seem to get an answer on whether the problem is systemwide, intermittent, temporary or whatever, but the agent had an answer readily available.
Doing the chat thing now to see if I can find an answer.
Answer from online chat: Search by Schedule works. But the normal Search or Search by Price doesn't.
I can't seem to get an answer on whether the problem is systemwide, intermittent, temporary or whatever, but the agent had an answer readily available.
Last edited by 18sas; Apr 1, 2009 at 9:13 am
Apr 1, 2009, 9:08 am
#4
Moderator: GLBT Travelers & Hyatt Gold Passport
Join Date: Jan 2000
Location: CVG
Posts: 15,300
I just had the same problem - but was able to resolve it with re-searching for the flights.
Apr 1, 2009, 9:12 am
#5
Join Date: Jul 2007
Location: KUL/TPA/OTP
Programs: UA1k, DL
Posts: 3,138
Same here. I didn't post because I didn't want to create another DL.Com issue thread. But seriously, this needs to be resolved. There is always something wrong on DL.Com. It's getting ridiculous...
Apr 1, 2009, 9:14 am
#6
FlyerTalk Evangelist
Join Date: Oct 2005
Location: Ponte Vedra Beach, FL
Programs: DL PM, HH Diamond, Fairmont Prem, SPG Gold, Priority Club Plat/IC Amb, AmEx Plat
Posts: 10,839
Apr 1, 2009, 9:37 am
#7
Join Date: Jul 2007
Location: KUL/TPA/OTP
Programs: UA1k, DL
Posts: 3,138
Since I have not flown UA in about six years, I will surely take your word for it.
Sorta off topic but..
My question to DL would be at what point are individuals held accountable for their performance. I worked in IT Development and UAT testing years back. The desktop application I managed had about 150 internal users and impacted thousands more on a daily basis (Chase Credit Card Apply By Phone App). If my users frequently had issues caused by my application, I would have been gone after fair warning.
Every change whether it be table driven or hard coded were put through several testing phases. We rarely had any issues due to the amount of testing we did. The analysts developed business requirements via Use Case Scripts, the developers/coders built the app based upon the Use Case Scripts, the Testers built Test Scripts mirroring the steps taken from the Use Case Scripts. In the end, every click, query, etc was tested. Everything... If issues were discovered, the app was rebuilt, and the same testing plan was followed once again.
Even when changes were being made to the switch which in theory should have absolutely no impact on our app, we were in there at 2AM est testing functionality.
It's really not that difficult. Someone needs to go.
Sorta off topic but..
My question to DL would be at what point are individuals held accountable for their performance. I worked in IT Development and UAT testing years back. The desktop application I managed had about 150 internal users and impacted thousands more on a daily basis (Chase Credit Card Apply By Phone App). If my users frequently had issues caused by my application, I would have been gone after fair warning.
Every change whether it be table driven or hard coded were put through several testing phases. We rarely had any issues due to the amount of testing we did. The analysts developed business requirements via Use Case Scripts, the developers/coders built the app based upon the Use Case Scripts, the Testers built Test Scripts mirroring the steps taken from the Use Case Scripts. In the end, every click, query, etc was tested. Everything... If issues were discovered, the app was rebuilt, and the same testing plan was followed once again.
Even when changes were being made to the switch which in theory should have absolutely no impact on our app, we were in there at 2AM est testing functionality.
It's really not that difficult. Someone needs to go.