Summary
An issue was resolved where the “Air Booking has changed” alert could be triggered incorrectly, even when no actual update had occurred for the specific booking.
Issue Details
The alerting logic relied on legacy code that did not always match incoming air‑booking updates to the correct booking. As a result, alerts could be created for the wrong booking within the same departure, or triggered when the air‑booking information had not changed.
Resolution
The alerting logic has been updated to ensure accuracy and prevent unnecessary notifications:
- The system now uses the booking number included in the air‑booking update to correctly associate the alert with the intended booking.
- Alerts are created only when the newly received air‑booking data is different from the previously stored information.
These improvements ensure that “Air Booking has changed” alerts are reliable, relevant, and only triggered when a genuine change occurs.