Re-booking delay after FS Crash

[DundeeFlyer]

Hi Konny,

I wonder if you can shed some light on this.

I some times have FS crash on me for various reasons and FlyNet client sets the flight back to booked state. However, I am unable to immediately re-start the flight after FS recovery and have to allow a significant time (sometime hours) before I can start the flight again. My questions are:

1- Is the re-booking script run by a cron, if so what is the set delay?
2- Can this delay be reduced at all?
3- When the flight is reset to bokked state so we get another 24 hours to fly from the time crash occured or from the initial date of booking?

Many thanks

M

[Konny]

When the flight is set back to booked state you normally should be able to re-start the flight immediately. But if the client is not able to set it back, and the flight is still shown as "enroute" on flight monitor, the website automatically sets it back after 10 minutes. And then you have another 24 hours to get the flight done.

So it shouldn't need hours for the flight to be available again. Maybe it's just a connection problem, or the database is down ( then the website also doesn't load up ).