Flight Info Alerts delivers operating as well as non-operating service numbers to the event hub.
In terms of schedule changes, both operating as well as non-operating services will be collated and sent to the event hub for your retrieval. To put it into perspective, imagine we have this fictional flight service:
XX123 JFK-ATL
With the above flight, if you have either a global alert or a port alert (all flights departing JFK or all flights arriving in ATL), all of the below events will be received by the event hub:
| carrierCode | flightNumber | comment010 | comment050 |
| XX | 123 | YY3210, ZZ4100 | null |
| YY | 3210 | null | XX123 |
| ZZ | 4100 | null | XX123 |
Service XX123 is the operating carrier and YY3210 and ZZ4100 are codeshared on XX123. All 3 events will be received by the event hub for retrieval with information (comment010 or comment050) tying the operating and non-operating flights together.
The comment010 and comment050 fields are named as a reference to IATA SSIM (Standard Schedules Infomration) DEI (Data Element Identifier) 010 and 050 sections.
If you have a carrier alert
The events received depends on the type of alert that you have created. Using the example above, if you have created an alert for:
All XX flights (carrier alert)
You will only receive the change event for the XX123 service and will not receive events for YY3210 and ZZ4100 as they do not fall under the 'XX' carrier code. However, you will still be able to infer this information via the comment010 field.
Similarly, if you created an alert for:
All YY flights (carrier alert)
You will only get updates for YY3210 and will not receive an additional event for XX123 or ZZ4100 as they do not have the YY carrier code. You will still be able to infer the actual operating service via the comment050 field but it would not be possible to see the other codeshared service e.g. ZZ4100.