Script doesn't wake up to check in

[ba221400]

On my last two attempts to use the script, it did not wake up to check in. I'm running with Docker, both in Linux and Win10.

Each time I get:

Flight information found, departing City, State at Nov 22 04:55PM
Too early to check in.  Waiting 7 hours, 54 minutes, 32.77192600000126 seconds

And then nothing. It doesn't attempt the check in at all. I do not see anything in the logs, other than the message above.

Any ideas why it's not waking up and running again?

[Raikia]

Are the # of hours, minutes, and seconds accurate? The timestamp accurate?

[pyro2927]

Any ideas why it's not waking up and running again?

When you say "waking up", is the machine it is running on going to sleep?

[stiggy87]

I had this happen to me. Machine was running, no sleep state. I also saw it print out a lot of the JSON response, so my guess something wasn't right with my clone.

[ba221400]

The # of hours, minutes, and seconds accurate; as-is the timestamp. The date on the host machine is accurate. I didn't check the date/time inside the container; I'll take a look at that tonight.

I've run it in the foreground, as well as backgrounding (-d) the container. When I said wake up, I was just thinking of the script sleeping, not the machine having to wake up.

[gnahum12345]

Had same problem but with a Mac and locally.

[justinrobinson1020]

Tried using this today and had the same problem. Running in docker and it never attempted to check in. I restarted the container after checking in manually and it recognized that I had done so and had the correct boarding info.

[cycomachead]

I kept a standard Python3 tab open, and this didn't work either...When I reran the command just to see it does correctly grab the current checkin.

[rjberm]

Any updates on here? I get the same. Mine says that the flight information is found, but too early to check in. What is it supposed to say if its working properly?