Oh no! We’re sorry, but there was a problem processing your request. Please try again
 

Anyone get this message consistently in Chrome:

Oh no! We’re sorry, but there was a problem processing your request. Please try again.#100900A ?

It is super annoying, and I can't seem to figure out what to do to fix it.

What were you attempting to do? Sometimes when having issues, clearing all DL site related cookies and starting over will fix things.

I've gotten that in the past with Chrome, using Incognito Mode (or a different browser) has always worked.

I'm getting it quite often lately - and usually at the payment page. But, only when I'm booking personal trips (Chrome), no issues when I book for business (Concur). I clear my cookies and history and it works. Just annoying.

I’m getting it when trying to search for flights. It seems that incognito used to work but doesn’t. Will try clearing my cookies

Are you using a VPN? It's becoming common for sites to throw up fake error messages like that rather than to outright tell the user that they are being fuzzed out because they're connecting from a VPN. Depending on how aggressive the blocking is, just switching exit node can clear the problem up but other times turning off the VPN is the only way.

had errors like this yesterday, on both Chrome and Edge. ended up just texting to change my booking.

Booking a new ticket for myself. Got a similar message trying to apply an eCredit from an (agent issued) unused ticket.



For context, the amount due from new ticket is less than the value of the eCredit.

Any experience/data point?

For me this seems to happen when I do a fairly large number of searches in a short period of time (eg scoping out the award flight options). Waiting a few minutes or using a different browser fixes the problem. I always wondered if this is a way to limit scripts from scraping their site.

Thanks for the feedback!

Initially, the purchase experience was based off a referral link from Google Flights. I then launched Delta.com directly from a different browser, and searched for the specific date and flight number myself - still the same error message when using eCredit :(

Anyway, the quoted fare bucket was dwindling down to 1, so I pulled the trigger without using the eCredit - of course, no issues with the booking on a cash fare :rolleyes:

Then I realized the purchased ticket omitted my SkyMiles # (despite being logged in during the purchase), and was auto-assigned a middle seat in row 48 :D. Eventually I was able to get one of the last available premium economy seats (sold as C+ on a domestic route) after the system (finally) recognized my Plat status.

Delta IT :td:

I get this a lot when trying to click "Purchase" after searching through the website to make a reservation.

Yes, happened to me when I was trying to book a ticket with miles. Called the reservations line and was told it was a 2 hour wait; got frustrated and just paid for the ticket regularly.

I just hit this for the first time trying to buy a ticket using an eCredit on the mobile web site. Switched to the Android app, saw the eCredit still had the full amount, so went through the process again and upon clicking purchase got "Your session has timed out", muttered a curse and thought I'd have to try a 3rd time but noticed the amount of the ticket had been deducted from the eCredit and indeed the reservation had gone through.

Then called to apply RUC since it had shown space available at booking and got through with basically zero hold time (around noon Pacific today)

for about the past hour I've been trying to change a flight ... the system works fine when bringing up the new flights, but as soon as I select the second segment it spins for a few seconds and throws this:

THANKS FOR YOUR PATIENCE

We’re experiencing temporary technical issues serving our customers on delta.com and the Fly Delta mobile app. We apologize for the delay, and are working to restore the site as quickly as possible. Some suggestions for your consideration:

• This page refreshes itself every 15 seconds, or you may try again later to complete your intended task.
• If you’re checking in, an agent will be happy to assist you at the airport.
• If you’re booking a flight or modifying an existing flight, please try again soon.
• For immediate assistance, you may contact a Delta representative at 1-800-221-1212, or via @Delta on Twitter.

PM line rep picked up in 9 minutes (estimate was 15); I read her the flight info that I wanted and she was *totally* befuddled as to why it wouldn't work ... tried to force it manually, no joy; escalated to a "senior staff member" who has been working on it for about 45 min ... more to follow


< update >
agent came back on the call and said Ticketing Support isn't actually seeing the second segment in their searches, so it may be a Schedule Change Saturday artifact that's likely to disappear this weekend :/
flights are DCA-BOS and BOS-SEA on Sat 19 Mar; just placeholders for now, but I was trying to do something with the placeholder flight I had for this Thursday instead of cancelling it

that aside, I suspect part of the problem is that it's only 3+07 between flights, so even though the system initially showed the multi-city option, some other logic (that more than a few of us have griped about for the past couple years) inhibits the ability to sell them as a sub-four-hour connection

< update update >
after a total of close to 2 hours, PM agent confirmed that it was indeed the 4-hour connection-vs-stopover time limit; GTS (Global Ticketing Support?) supervisor was able to override and force the flights to ticket

not everything was perfect — she quoted me an add-collect close to $175 more than I was expecting because it was a pair of “Z” fares end-on-end (even though the system had originally displayed the entire trip in “I”); after I asked her to reprice DCA-BOS in coach she came back with a very happy “Good news! You’ll actually get a credit of $42!” — uh, no, I still want BOS-SEA in F” — end result was about $45 over target but not terrible

I've been getting this little lovely on Chrome the past week or so. Very annoying...basically renders the website useless for any transaction
Nothing changed on my end versus before.
Have to do everything on the phone app...

Bad Request

Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.