Error reports and suggestions for OLCI/mobile CKI
#91
Join Date: Jul 2009
Posts: 69
I suppose this is to be expected as it's a booking for two passengers, but it's a real shame I can't have the BP on the AF's mobile app.
What would be great is having all BPs and then picking one or just having the option to download one. Surely it's something that can be done
Had I booked the flights as individual tickets, it would be fine. But for the sake of convenience, I booked them together, and as a result, you are inconvenienced by the inability to have the BP on your phone
What would be great is having all BPs and then picking one or just having the option to download one. Surely it's something that can be done
Had I booked the flights as individual tickets, it would be fine. But for the sake of convenience, I booked them together, and as a result, you are inconvenienced by the inability to have the BP on your phone
#94
Join Date: Jan 2008
Location: in your favourite lounge, clearing the whole buffet
Programs: LH Maximizer of the year, BA Blue Label killer
Posts: 1,001
Grr, OLCI on AF and KL websites override my DL FFN entered in the PNR with the Flying Blue FFN automatically, maybe because it is booked as an award flight on FB? There is no way leaving the DL FFN except not checking in online.
#95
Join Date: Oct 2011
Programs: FB Platinum for Life
Posts: 1,019
I recently tried to do OLCI at klm.com for a KL-coded, ticketed and operated TATL flight, for myself and Mrs KQ321 - travelling together but on separate PNRs.
Having started OLCI for one of us, and selected 'add passenger', the system correctly found the other pax. However, the following screen asked to 'confirm personal details' (ie: gender, DoB, nationality, residence and FFN) for each pax - and although these were correctly entered for both of us, the system wouldn't proceed beyond this point, but gave the following error message:
So, it appears there is some kind of (transient?) problem with the personal information/API data stage, when pax on multiple PNRs attempt to check-in together...
PS: I realise I've posted quite a few error reports in this thread in recent months, so perhaps I should point out that for the vast majority of flights (especially single sector trips within Europe), OLCI has worked perfectly...
Having started OLCI for one of us, and selected 'add passenger', the system correctly found the other pax. However, the following screen asked to 'confirm personal details' (ie: gender, DoB, nationality, residence and FFN) for each pax - and although these were correctly entered for both of us, the system wouldn't proceed beyond this point, but gave the following error message:
Unfortunately something went wrong while updating your personal details. Please try again later, or check in at a self-service machine or at the desk at the airport. We are sorry for the inconvenience! [005.001.000]
Doing OLCI for each of us individually worked fine - the (same) personal details were accepted, and it then moved to another personal details screen (I think asking API data for the USA). Data entered here was accepted, and we were able to (individually) complete OLCI.So, it appears there is some kind of (transient?) problem with the personal information/API data stage, when pax on multiple PNRs attempt to check-in together...
PS: I realise I've posted quite a few error reports in this thread in recent months, so perhaps I should point out that for the vast majority of flights (especially single sector trips within Europe), OLCI has worked perfectly...
#96
Join Date: Jul 2009
Posts: 69
I recently tried to do OLCI at klm.com for a KL-coded, ticketed and operated TATL flight, for myself and Mrs KQ321 - travelling together but on separate PNRs.
Having started OLCI for one of us, and selected 'add passenger', the system correctly found the other pax. However, the following screen asked to 'confirm personal details' (ie: gender, DoB, nationality, residence and FFN) for each pax - and although these were correctly entered for both of us, the system wouldn't proceed beyond this point, but gave the following error message:
So, it appears there is some kind of (transient?) problem with the personal information/API data stage, when pax on multiple PNRs attempt to check-in together...
PS: I realise I've posted quite a few error reports in this thread in recent months, so perhaps I should point out that for the vast majority of flights (especially single sector trips within Europe), OLCI has worked perfectly...
Having started OLCI for one of us, and selected 'add passenger', the system correctly found the other pax. However, the following screen asked to 'confirm personal details' (ie: gender, DoB, nationality, residence and FFN) for each pax - and although these were correctly entered for both of us, the system wouldn't proceed beyond this point, but gave the following error message:
Unfortunately something went wrong while updating your personal details. Please try again later, or check in at a self-service machine or at the desk at the airport. We are sorry for the inconvenience! [005.001.000]
Doing OLCI for each of us individually worked fine - the (same) personal details were accepted, and it then moved to another personal details screen (I think asking API data for the USA). Data entered here was accepted, and we were able to (individually) complete OLCI.So, it appears there is some kind of (transient?) problem with the personal information/API data stage, when pax on multiple PNRs attempt to check-in together...
PS: I realise I've posted quite a few error reports in this thread in recent months, so perhaps I should point out that for the vast majority of flights (especially single sector trips within Europe), OLCI has worked perfectly...
Strangely, it asks for my nationality, something which it hasn't done in recent times, despite me booking this ticket exactly the same way as my previous ones.
Either way, no matter what I try and how I try it, just cannot get past this.
Also, on my previous flight (also a LHR-CDG), I had an automatic check-in, something I've only ever had on previous domestic AF flights.
I received an email this morning saying that due to a technical error, I wasn't checked in automatically.
I presume the root cause is the same, but why?
#98
Join Date: Jul 2009
Posts: 69
Bonjour Ben from a fellow TV engineer working in Paris
I eventually managed to fix this and check in although it's a somewhat convoluted process.
The reason (in my case) for the inability was because it had somehow lost my passport / nationality information.
It's misleading because the error is just a number and at no point does the check-in process suggest what is missing.
The way I did it was to log into my profile on the full website, then in my personal details, add the documents.
Once that's done and all saved. Log out of your account, then log back in. After I did that, I was able to check in online.
Now tt could be that you already have the details saved for yourself, but if this is the first time you're travelling with your son, his details aren't present hence the problem.
It could also be that you cannot check-in minors online, I don't know, but it's worth checking you have all the passenger's details in your profile. I think you can add others too (I seem to remember seeing that option on the mobile app).
Bonne chance!
Xavier
I eventually managed to fix this and check in although it's a somewhat convoluted process.
The reason (in my case) for the inability was because it had somehow lost my passport / nationality information.
It's misleading because the error is just a number and at no point does the check-in process suggest what is missing.
The way I did it was to log into my profile on the full website, then in my personal details, add the documents.
Once that's done and all saved. Log out of your account, then log back in. After I did that, I was able to check in online.
Now tt could be that you already have the details saved for yourself, but if this is the first time you're travelling with your son, his details aren't present hence the problem.
It could also be that you cannot check-in minors online, I don't know, but it's worth checking you have all the passenger's details in your profile. I think you can add others too (I seem to remember seeing that option on the mobile app).
Bonne chance!
Xavier
#101
Join Date: Jul 2009
Posts: 69
Argh!
FFS, they've done it again.
Went to check in online using their Android App, and I knew it wasn't going to work when it asks for nationality... Same error code: 005.009.111
I've added the passport to the app again, for some reason it was deleted. But still cannot check in.
I've logged out and back in, no change.
I've tried checking in on the normal web page on the PC, same problem.
This is sooo frustrating. Happens every now and then for no reason. I book my tickets in exactly the same way.
It's not just ATC in France that are on strike, it's AF's systems too!
Went to check in online using their Android App, and I knew it wasn't going to work when it asks for nationality... Same error code: 005.009.111
I've added the passport to the app again, for some reason it was deleted. But still cannot check in.
I've logged out and back in, no change.
I've tried checking in on the normal web page on the PC, same problem.
This is sooo frustrating. Happens every now and then for no reason. I book my tickets in exactly the same way.
It's not just ATC in France that are on strike, it's AF's systems too!
#103
Join Date: Mar 2008
Location: Zanzibar
Programs: Flying Blue
Posts: 1,319
tried checking in for my Y flight to CUR tomorrow. No allocated seats?? and no seat plan.. now hoping I will have some decent seats tomorrow as Plat..
Twitterted KLM this morning but no reply...
Twitterted KLM this morning but no reply...
#104
FlyerTalk Evangelist
Join Date: Aug 2009
Location: Paris, France
Programs: AF/KL Flying Blue Platinum for life/Club2000 Ultimate, Accor ALL Diamond
Posts: 21,922
I did't want to open a new thread for this, but there are some interesting bugs at the moment in the AF app. Look at the lounge info (this is a Schengen flight in Y out of 2F)
I was secretly hoping it was a new Ultimate benefit , but no...just a bug.
I was secretly hoping it was a new Ultimate benefit , but no...just a bug.