You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My suggestion is that we give a grace period of 5 or 10 minutes where we do nothing, just leave the airplane as is, but we flag it as "disconnected" in the UI and API. We build a function to deal with disconnected aircraft - process them like a normal update, BUT use previous heading, speed and altitude to move them like it would normally do.
After grace period, remove it, but keep a record of it when we have a historical database, and if an airplane reconnects with the same details, including flightplan later, continue existing flight?
No description provided.
The text was updated successfully, but these errors were encountered: