sw-check-in getting 404 response for international flights

[ScottBishop]

I have had about 5 check-in's fail recently and I think something is wrong with the sw-check-in lambda check-in request. It found the reservation when scheduling the check-in which is why I opened this up as a separate issue than #50 but they could be related. I am getting 404 responses.

Most of the failures are international flights (Mexico -- all passengers had passport info entered beforehand) but one is domestic which is concerning. Logging wasn't helpful so I added more logging in hopes that I'll get more info on the return flight checkin failure in a few days.

[INFO]	2018-11-20T15:55:06.650Z	847af378-2df5-4322-806c-bd87d54149a4	Checking in [{'firstName': 'John', 'lastName': 'Doe'}] (XXXXXX)
<<Response [404]>>
[ERROR]	2018-11-20T15:55:08.546Z	847af378-2df5-4322-806c-bd87d54149a4	Reservation XXXXXX has been cancelled

Checking in manually with the same names and confirmation numbers as the cloudwatch logs worked which makes me think this isn't related to the parser.

Do you have a way of manually executing the swa.py script or sw-check-in lambda? Check-ins are repeatable so I might be able to get more debug info today if I attempt again with more logging.

[DavidWittman]

Thanks for reporting this... I had some successful check-ins this morning for domestic flights, but I'd appreciate you digging in if you find the time. You can install the requirements from `lambda/requirements.txt` and then just run the python interactive shell and import the swa lib. (while in the lambda dir) ``` $ python Python 3.6.3 (default, Oct 4 2017, 06:09:15) [GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37)] on darwin Type "help", "copyright", "credits" or "license" for more information.

>> from lib import swa >> help(swa.check_in) >> swa.check_in([{'firstName': 'John', 'lastName': 'Doe'}], 'ABC123')

```

…

On Tue, Nov 20, 2018 at 10:53 AM Scott Bishop ***@***.***> wrote: I have had about 5 check-in's fail recently and I think something is wrong with the sw-check-in lambda check-in request. It found the reservation when scheduling the check-in which is why I opened this up as a separate issue than #50 <#50> but they could be related. I am getting 404 responses. Most of the failures are international flights (Mexico -- all passengers had passport info entered beforehand) but one is domestic which is concerning. Logging wasn't helpful so I added more logging in hopes that I'll get more info on the return flight checkin failure in a few days. [INFO] 2018-11-20T15:55:06.650Z 847af378-2df5-4322-806c-bd87d54149a4 Checking in [{'firstName': 'John', 'lastName': 'Doe'}] (XXXXXX) <<Response [404]>> [ERROR] 2018-11-20T15:55:08.546Z 847af378-2df5-4322-806c-bd87d54149a4 Reservation XXXXXX has been cancelled Checking in manually with the same names and confirmation numbers as the cloudwatch logs worked which makes me think this isn't related to the parser. Do you have a way of manually executing the swa.py script or sw-check-in lambda? Check-ins are repeatable so I might be able to get more debug info today if I attempt again with more logging. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#53>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AArmL6m0d9At012lpC2Gs31Zv7t4FfATks5uxDOWgaJpZM4Yrhbs> .

[ScottBishop]

Ok here is the response. I am able to lookup the same reservation on https://mobile.southwest.com/check-in with no issues.

('response: ', {u'message': u'Service not found', u'code': 404411182, u'infoList': [{u'value': u'https://api-travel-int-a.pdc.swacorp.com/v1/air-travel/reservations/record-locator/ABC123/travelers/boarding-passes', u'key': u'url'}], u'requestId': u'no-exp-id:NTCDzH4CTByIVQOPw5T3MQ:air-travel', u'httpStatusCode': u'NOT_FOUND'})

lib.exceptions.ReservationCancelledError: status_code=404 data={'names': [{'lastName': 'John', 'firstName': 'Doe'}]} msg="Service not found"

[ScottBishop]

I've confirmed this is for international travel only. I had previously entered all my passport information, so I don't think that was the issue. Still unclear why this is happening.