Hi,
It looks like the call ‘SearchBirdseyeInFlight’ to identify diversions isn’t working, and hasn’t been working for a few weeks. I’m wondering if there is a timeframe for fixing this bug.
Thanks!
Any updates on this? I have tried calling the ‘support’ number but they are of zero help and refer me to this message board. Except no one has responded to this. Thanks.
I have opened up a ticket internally for our team to look into this.
Any updates on this from the last week?
It seems to be working fine in my testing, and I’m not aware of any changes that would have specifically broken diversion tracking:
https://flightxml.flightaware.com/json/FlightXML2/SearchBirdseyeInFlight?query={true%20diverted}
It looks to me that it was raised quite a long time ago and that this, I see the last response from you @bovineone is that it worked for you. I checked it yesterday, and I checked it today and I can confirm it is not working. For this query:
http://flightxml.flightaware.com/json/FlightXML2/SearchBirdseyeInFlight?query={true diverted}
It always returns “error”: “NO_DATA no data available”.
And I checked https://flightaware.com/live/diversions.rvt?;offset=0;order=actualdeparturetime;sort=DESC to see that Flight Aware is “aware” of any given diverted flghts at the time of calling that API. I had one flight that was diverted and had still 15 minutes to land, but nothing from the API.
Is is something that will stay like this, be addressed, fixed? Any response will be really appreciated.
In late 2018 (after my post) there was some internal infrastructure changes that unintentionally caused the diverted field to no longer work in the SearchBirdseyeInFlight method. We are beginning to analyze the effort to re-support that functionality. Thanks for bringing this regression to our attention.
This functionality has been restored and should be working again.
Great news bovineone! I’ve checked and it looks good!
1 Like