Error data in PUSH alerts

I have noticed today I started receiving incorrect data in PUSH alerts (XMLv2 service). The service is running for months, no changes were made. The amount of failure messages in my case is more than 80%. Please look on this example:

{“long_desc”:“Wizz Air #1752 (A320) departed Turku (TKU) at 15:20 EEST enroute to Gdansk Lech Walesa (GDN) for an estimated arrival at 15:20 CEST”,“short_desc”:“WZZ1752 (A320) departed TKU @ 15:20 EEST for GDN ETA 15:20 CEST”,“summary”:“WZZ1752 has departed TKU for GDN”,“eventcode”:“departure”,“alert_id”:26874952,“flight”:{“faFlightID”:“WZZ1752-1536668577-airline-0329”,“error”:“Extended details unavailable: build_json_flight_body_v1 could not load details”}}

Dear FA staff - please advise this CRITICAL issue as the service is not working.

Hello,

We’ve got a case open on our side and we’re investigating the alerts that are missing bodies for Wizz Air flights.

It is not only WizzAir. Please see below other examples:

{“long_desc”:“Lot - Polskie Linie Lotnicze / Blue Air #408 (B738) has just filed a flight plan. It is scheduled to depart from Dusseldorf Int’l (DUS) at 20:00 CEST środa (22 sie) heading for Warsaw Frederic Chopin (WAW) for an estimated arrival at 21:50 CEST środa (22 sie).”,“short_desc”:"BMS408 (B738) filed to depart DUS @ Śr (22 sie) 20:00 CEST for WAW @ ETA 21:50 CEST (22 sie) ",“summary”:“BMS408 filed a flight plan DUS → WAW”,“eventcode”:“filed”,“alert_id”:26467321,“flight”:{“faFlightID”:“BMS408-1534742769-airline-0185:0”,“error”:“Extended details unavailable: build_json_flight_body_v1 could not load details”}}

{“long_desc”:“SAS / Cityjet #756 (CRJ9) departed Gdansk Lech Walesa (GDN) at 09:40 CEST enroute to Copenhagen (CPH) for an estimated arrival at 10:24 CEST\n\nDestination (Copenhagen / CPH): Terminal 3”,“short_desc”:“BCY756 (CRJ9) departed GDN @ 09:40 CEST for CPH ETA 10:24 CEST”,“summary”:“BCY756 has departed GDN for CPH”,“eventcode”:“departure”,“alert_id”:26467286,“flight”:{“faFlightID”:“BCY756-1534829171-airline-0019”,“error”:“Extended details unavailable: build_json_flight_body_v1 could not load details”}}

{“long_desc”:“KLM #1921 (E190) departed Amsterdam Schiphol (AMS) at 15:56 CEST enroute to Gdansk Lech Walesa (GDN) for an estimated arrival at 17:23 CEST”,“short_desc”:“KLM1921 (E190) departed AMS @ 15:56 CEST for GDN ETA 17:23 CEST”,“summary”:“KLM1921 has departed AMS for GDN”,“eventcode”:“departure”,“alert_id”: 26467288,“flight”:{“faFlightID”:“KLM1921-1534829160-airline-0107”,“error”:“Extended details unavailable: build_json_flight_body_v1 could not load details”}}

Thanks for the extra examples. We’re should have this have this resolved sooner rather than later.

Do you have any update on this issue?

Hi,

A minor update to alert handling was published about a week after your initial report to prevent this error case. Are you still seeing cases of the “could not load details” error?

No, at the moment everything seems to be OK. Thank you for the update.