Replies: 5 comments 11 replies
-
Looks like there is a departed flight branch currently in development stage and hopefully the merge to master may fix this issue. |
Beta Was this translation helpful? Give feedback.
-
Thank you very much. Quick question - Today I checked-in a flight to las
vegas, but got C10. It tried many times as per log but failed. Also it
started trying from 5 seconds before the actual time and then kept making
many attempts. Any way to change that setting? or how to find the root
cause?
…On Sun, May 12, 2024 at 1:24 PM Joey Holtzman ***@***.***> wrote:
To apply the fix until it’s merged, you can run git pull && git checkout
develop && pip install -r requirements.txt and the rerun the script to
make sure it checks you in correctly. I’ll merge the fix soon in a new
minor update.
—
Reply to this email directly, view it on GitHub
<#260 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIMFCZE3X2JLQ4X44Q3LRTDZB6XVLAVCNFSM6AAAAABHS5SET2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TIMBYHAZDG>
.
You are receiving this because you authored the thread.Message ID:
<jdholtz/auto-southwest-check-in/repo-discussions/260/comments/9408823@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
Here is the log, not sure where it went wrong as the final completion was
26 secs later which delayed the process to get C10
2024-05-12 13:35:22 DEBUG Process-1:1[checkin_handler:105]: Lock released
2024-05-12 13:35:22 DEBUG Process-1:1[checkin_handler:109]: Sleeping until
check-in: 1772 seconds...
2024-05-12 14:04:55 DEBUG Process-1:1[checkin_handler:128]: Attempting to
check in
2024-05-12 14:04:55 DEBUG Process-1:1[checkin_handler:156]: Submitting
check-in with a POST request
2024-05-12 14:04:55 DEBUG Process-1:1[checkin_handler:188]: Making GET
request to check in
2024-05-12 14:05:15 DEBUG Process-1:1[utils:34]: Successfully made request
after 5 attempts
2024-05-12 14:05:15 DEBUG Process-1:1[checkin_handler:194]: Making POST
request to check in
2024-05-12 14:05:26 DEBUG Process-1:1[utils:34]: Successfully made request
after 5 attempts
2024-05-12 14:05:26 DEBUG Process-1:1[checkin_handler:164]: Successfully
checked in after 1 attempts
2024-05-12 14:05:26 DEBUG Process-1:1[notification_handler:103]: Sending
successful check-in notification...
…On Sun, May 12, 2024 at 2:20 PM Joey Holtzman ***@***.***> wrote:
The 429 you are receiving is probably what’s seen in #201
<#201> but with
people have been getting the same error with check-ins more often now.
Any way to change that setting? or how to find the root cause?
The script is configured to start checking in 5 seconds early in case the
Southwest servers are a little ahead. It’s also to hopefully make the
check-in go through as early as possible. There’s no way to configure that
setting though.
—
Reply to this email directly, view it on GitHub
<#260 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIMFCZBNDJVM5RNEWSEUPX3ZB66JRAVCNFSM6AAAAABHS5SET2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TIMBZGY4DQ>
.
You are receiving this because you authored the thread.Message ID:
<jdholtz/auto-southwest-check-in/repo-discussions/260/comments/9409688@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
The original post is for trip from Houston to STL 2 days before. This one C10 is from STL to Las Vegas (ran the script today without any 429 response), but the log shows 6 attempts. |
Beta Was this translation helpful? Give feedback.
-
I did GIT PULL and GIT CHECKOUT for latest updates from DEVELOP branch, but the CHECKIN didn't go through for one of the flights leaving LAS VEGAS to STL tomorrow 5:05 PM PDT. See the below logs, Looks like it did tried 20 attempts, but got the error as "Something went wrong" (I used -debug--screenshots option) The time difference of Attempting to check-in and Submitting Check-in with POST request is almost 3 minutes. 2024-05-15 16:36:18 DEBUG Process-1:1[checkin_handler:105]: Lock released
} |
Beta Was this translation helpful? Give feedback.
-
The below script ran on past the first leg trip, but the script is still trying to check-in for prior completed trips (Date/Time condition check may require after retrieving the reservation details)
$ python southwest.py
Successfully scheduled the following flights to check in for ABC XYZ:
Flight from St. Louis to Houston (Hobby) on 2024-05-03 3:25 PM CDT
Flight from Houston (Hobby) to St. Louis on 2024-05-10 9:30 PM CDT
Checking in to flight from 'St. Louis' to 'Houston (Hobby)' for ABC XYZ
Successfully scheduled the following flights to check in for AAA BBB:
Flight from Houston (Hobby) to St. Louis on 2024-05-11 5:15 AM CDT
Failed to check in to flight CCCCCC for ABC XYZ. Reason: Too Many Requests 429.
Check in at this url: https://mobile.southwest.com/check-in
Successfully scheduled the following flights to check in for BBB CCC:
Flight from St. Louis to Houston (Hobby) on 2024-05-03 3:25 PM CDT
Flight from Houston (Hobby) to St. Louis on 2024-05-10 9:30 PM CDT
Checking in to flight from 'St. Louis' to 'Houston (Hobby)' for BBB CCC
Failed to check in to flight CCCCCC for BBB CCC. Reason: Bad Request 400.
Check in at this url: https://mobile.southwest.com/check-in
Beta Was this translation helpful? Give feedback.
All reactions