Return flight not properly checked in.

[CoderFromCali]

The return flight for my last trip was not properly checked in. The script tried to check in at the proper time, but somehow didn't actually check in the return flight. Instead, it captured the boarding information from the outbound flight. This return flight was on the same day as the outbound flight. There were also two people traveling on the same reservation. I'm not sure if these are factors in the problem.

Here is the log:

swchkin-error.log

[rjberm]

Sorry not answer to your question but when you run the code did it say too early to checkin and you just left it running until the day of?

[CoderFromCali]

Yes, you can see in the log where it initially waited here:

On line 1 (timestamp 2021-05-27 19:55:22) it attempted to check in but was too early.
Then on line 237 (timestamp 2021-05-27 19:55:36) it found flights to check in:

Flight information found, departing , at May 29 06:30AM
Too early to check in. Waiting 17 hours, 34 minutes, 18.980916000000434 seconds
Flight information found, departing , at May 29 05:40PM
Too early to check in. Waiting 28 hours, 44 minutes, 18.640918000004604 seconds

Then on line 387 (timestamp 2021-05-28 13:30:05) it attempted to the first check in.
Then on line 512 (timestamp 2021-05-28 13:30:08) it got both boarding positions.
Then on line 574 (timestamp 2021-05-29 00:39:56) it attempted to log in again.
Then on line 699 (timestamp 2021-05-29 00:39:56) it got the same boarding positions again that it did on line 512.

Unfortunately there's no time stamps in the way this log was exported. There were, however, timestamps in the UI, and they showed that it waited after getting the first boarding positions until the next check in time. Here are some screenshots showing the time stamps:

[rjberm]

I'm running the code in a raspberry so all I see is the following

Flight information found, departing "airport" at Dec 20 6:00AM
Too early to check in. Waiting 1243 hours, 52 minutes, 40.87 seconds
Flight information found, departing "airport" at Jan 03 06:30PM
Too early to check in. Waiting 1592, 22 minutes, 50.52 seconds

I don't see anything beyond that... If I close the command line, I assume the script will shut down.

So do you recommend I run the code only 1-2 days prior to the 24 hours prior to the flights? I guess 2 months from now might be too far.

I also don't see a UI like the image you showed!

[rjberm]

There's also 4 people in the reservation, would it check in for all 4?

[CoderFromCali]

There's also 4 people in the reservation, would it check in for all 4?

There were only two people in the reservation. The expectation is that it would check in both for the outbound flight and then both again for the return flight. The logs and timestamps bare this out.

[CoderFromCali]

I'm running the code in a raspberry so all I see is the following

Flight information found, departing "airport" at Dec 20 6:00AM Too early to check in. Waiting 1243 hours, 52 minutes, 40.87 seconds Flight information found, departing "airport" at Jan 03 06:30PM Too early to check in. Waiting 1592, 22 minutes, 50.52 seconds

I don't see anything beyond that... If I close the command line, I assume the script will shut down.

So do you recommend I run the code only 1-2 days prior to the 24 hours prior to the flights? I guess 2 months from now might be too far.

I also don't see a UI like the image you showed!

The UI I'm using is from the Docker app on a Synology. I kick off the container with my confirmation number as soon as I make the reservation. The container runs until the return flight is checked in, it just runs in the background on the Synology.

[rjberm]

got it, thankyou for the update!