Can't input flight because forced to enter duration

[Gnopps]

I'm trying to enter a new flight but every time I get the below message to enter manual duration:

I am using Firefox on windows and have entered: airports, carrier, aircraft, leisure/work, and class. I have no touched the duration-input and it is completely empty.

I have tried to delete all site cache & cooked, followed by a relogin but problem remains.

[reedy]

I've seen this a few times, but not consistently :/

[rogueglobal]

I am getting this error consistantly on the most recent versions of Chrome on Windows 10 Pro and Windows 11 Pro.

[reedy]

Here's a stupid workaround...

If you enter the destination (To) before the origin (From), does it work?

If I do From then To, I see this issue. If I do From then To, I don't...

[rogueglobal]

Unfortunately, neither of these workarounds work for me.

I had it work properly once yesterday after I had not used the site in a few weeks. But, as soon as I tried adding a new flight after the string of four flights that I entered, it went haywire again.

More than happy to assist with additional diagnostics or troubleshooting!

[reedy]

Screen.Recording.2024-01-03.at.19.01.23.mov

Screen.Recording.2024-01-03.at.19.01.41.mov

[Gnopps]

The workaround I use is to enter a duration, save, then edit the flight and delete the duration.

[rogueglobal]

Screen.Recording.2024-01-03.at.19.01.23.mov
Screen.Recording.2024-01-03.at.19.01.41.mov

Following the steps exactly in your second video, I am not able to get an auto-calculated duration.

Historically, I never have put in a departure time either. But attempted per your video to no luck.

[reedy]

It seems the recalculation just being isn't triggered consistently on some flow paths; it shouldn't be a difficult fix, but I'm not having much luck finding where to start

[dnowacki]

Ran into this today. I tried the workaround of entering a start/end time and then deleting it, but then I end up with an unrealistically short flight time (e.g., SFO->DFW showing flight time of 00:30). Happening on both Safari and Firefox, macOS 12.7.2 for me.

[sohantanna]

I am still getting this today.