I tried to check-in for an AMS-JFK flight using the app. I entered everything, then at the last step it said "oops, there's a problem. Try again later". After a few rounds of that, I tried checking in on the website. It also reported an error at the end, but this time it said KLM is handling the flight (it's a DL marketed and operated flight), here's a link to KLM. I went to the KLM website and found it wanted contact information (my email, phone and address), all of which DL has. After supplying that info to KLM, the check-in was successful. I could download the BP and a bit later the BP showed up in the DL app.

In the past I've sometimes had problems checking in on the web, but the app worked. This is a new one for me.

Is this a known glitch?

ELGRACHT 15 AMSTERDAM

For DL-operated flights departing from AMS or CDG, it can often be a little wonky since the flights are handled by KL & AF, respectively. Sometimes I've been able to get a DL BP in the app and sometimes I haven't - no real rhyme or reason. Therefore, not surprised to hear you ran into an issue, but there's no real solve as far as I know other than to give it a try and see if it works; otherwise, if not, to stop at the counter at the airport.

^ The solve was to use delta.com. I'm much happier now that I have BP in hand and in app.

"Handled by" means KLM or AF do the ground stuff other than BPs?

DL sends necessary data to KL who does all checkin and departure handling. After the flight is departed and closed out, KL sends DL back a file of the passengers boarded etc. KL controls the standby list.

For my recent AMS-BOS flight, I checked in online the evening before and ended up being routed to the KL checkin site and checked in there. As you did, I had to give some further information. Perhaps all information KL wants is not included in the upload of passenger data sent by DL. In the end I had a KL boarding pass and all went smoothly.

There is usually one DL red coat at the gate, but otherwise, KL/AF do all the standard ground handling - co-located check-in desks, etc.

As a datapoint, departing CDG a few days ago ran into the same issue. App wouldn�t check us in, just kept a loop of error messages with the occasional �We�ve found your reservation, but check in must be completed by AF� (even though we were on solely DL metal).

Didn't attempt to check in via AF website. Just got to the airport early and had no issues checking in at the DL counter. The agent was very confused where our final was (ANC) and actually applied an international-international purple tag that, I didn�t find out until we landed in the US, actually said not to send to customs belt in the US! It said to transfer to the next international flight. Thankfully that did not happen, and we were able to claim and re-check as normal. So, lesson learned, watch the CDG contract/AF agents.

Even more amusing when landing in ANC, one of our three bags did not appear at the carousel, despite receiving the �bag on plane� scan departing SEA. I went to the baggage office and my bag was sitting there at the desk. The agent was very confused how it got there as apparently the baggage claim tag on the bag had gotten ripped off. (Must have gotten snagged on a belt loader somewhere). She said she didn�t know how she could officially release it to me. I showed her my name on the bag, my boarding pass, my AF-issued claim check, and even pointed out the little white sticker from the tag that had disappeared was on the side of the bag, matching my claim check number. To which she replied �Oh wow! I never knew those little stickers had numbers on them.� I explained they were a backup for exactly this purpose. She then released the bag to me. I swear agents are getting less and less training and we, as frequent fliers, know more about the system than they do.

That was a better app error message. The app never told me to try KLM. Maybe if I did a few more rounds it would have.

Yeah, it wasn�t an instantaneous �try AF� which at first caused me to worry something might be messed up (we had IROPs on the way over so was worried something had screwed up the return). But after a few tries we got the AF notice and it seemed to only appear randomly during the occasional other attempts I made before going to the airport.