This release includes a fix for an issue where Group Held Spaces were not correctly applied to Departure availability, resulting in inaccurate departure counts.
In certain scenarios—such as creating a new group from an existing booking, linking additional bookings to a group, or working with imported group data—held spaces were being recorded on the Group but not reflected on the associated Departure. This caused the Departure to show incorrect availability.
Additionally, in some cases, guests added to a booking were not properly associated with the group, which contributed to incorrect held‑space calculations.
What’s Been Fixed
- Corrected the logic that updates Departure Held Spaces when groups and bookings are created or modified.
- Ensured that all guests on a booking are properly associated to the group, allowing held‑space calculations to remain accurate.
- Updated backend validation to ensure the p15_spacesheld value is consistently and correctly calculated.
- Improved handling of group and guest associations so that Booking 2.0 and backend data remain in sync.
Departure availability now accurately reflects Group Held Spaces across all supported scenarios, ensuring correct counts for planning and booking workflows.