Not sure if anyone seeing the same? but this is another disconnect happened in this week. Telling me it is no longer connected while I left the simfly client alone.
The API key is regenerated so no worry. I had to regenerate to get it working again.
Not sure if anyone seeing the same? but this is another disconnect happened in this week. Telling me it is no longer connected while I left the simfly client alone.
The API key is regenerated so no worry. I had to regenerate to get it working again.
I’ve experienced a similar issue. My API key disappeared on its own even though I didn’t do anything after flying for 13 hours. About one hour before landing, it disconnected, which was really frustrating and ended up wasting a huge amount of my flight time for nothing. This seems like a recurring system issue. I encounter it about 1–2 times a month. It would be great if they could fix it permanently.
Hi,
thank you for all the reports.
This is a bug we have been dealing with for a long time, and we are now fully focused on finding a definitive solution. In the past, we have already intervened several times to try to fix it, including making changes to the architecture, but the problem kept coming back.
In some cases, the issue may also be related to a client disconnection lasting more than 15 minutes. If the connection drops during the flight and then comes back, it can happen that the API key is lost without you noticing it. For this reason, starting tomorrow the new client will clearly notify you if it gets disconnected, so you will be able to reconnect it within the allowed 15 minutes. This will also give us more useful information to better monitor and verify the issue.
We now have a much clearer understanding of the root cause. Within this week, we will do our best to resolve this bug permanently, as it is essentially one of the last long-standing issues still open.
As for the rare bug that shows the flight analysis message on very long flights, asking you to contact support when the processing takes too long, that should already be fixed starting tomorrow.
Thank you again for your patience and continued support.