Release Notes – v3.2.4-rc1

13 July 2026 (1f973f7)

Unable to amend a River Tour Booking

V3-232

Fixed an issue where amending a River Tour booking in Reservations would fail if the original timeslot had been cancelled. Previously, the system checked against the time of the current booking, preventing the amendment from being confirmed. Amendments can now be made directly without needing to change the date back and forth as a workaround.

Add 30s cancelling DB query timeout to report endpoints

V3-234

Fixed an issue where certain report queries (e.g. eFinancial exports) could run indefinitely in the database after the API request had timed out, holding connections and consuming resources. A 30-second cancelling timeout is now applied to all report query executions, ensuring long-running queries are stopped at the database level and connections are freed promptly.

Lead member details edit blocked by required fields on additional member details

V3-235

Fixed an issue in Reservations where editing lead member details on a Joint (or higher) membership was blocked if an additional member had incomplete required fields (e.g. missing date of birth). The Save Changes button would remain greyed out even after completing the required fields. Lead and additional member details can now be edited independently without one blocking the other.

Membership Orders - Lead Member details missing on some orders

CORE-8975

Some migrated membership orders (imported before any subsequent amendment) displayed no lead-member details even though the data existed. The order projection now handles order histories that predate the CustomerDetailsProvidedV2 event format correctly

Release Notes – v3.2.4-rc2

17 July 2026 (0d5897f)

Here are your customer-facing release notes for v3.2.4-rc2:

Publish flow can silently drop rows from shared materialized views (race behind V3-259 P1)

V3-265

Fixed a race condition where saving an entity in Admin could cause its row to be dropped from shared materialised views if the publish hook fired before the database transaction committed. This could result in entities (e.g. locations) disappearing from search, redeem, and scan operations. The publish hook now defers until after the transaction commits, and search/redeem operations have been hardened to tolerate a temporarily missing entity row rather than failing entirely.

This issue permanently resolved the issue raised in Freshdesk case 5433 / V3-259 - HCG unable to search for or redeem orders.

HRP - V3 Roll Out - Creation of 1 order with 2 identical bookings on B2C WEB journey

V3-258

Fixed an issue where customers could end up with duplicate bookings on a single order during the B2C web journey, resulting in double charges. Customers were seeing the correct amount at the point of payment but receiving confirmation of two identical bookings. This has been resolved to prevent duplicate bookings from being created on a single order.

HRP - Abandoned order requires investigation (DVO8FRP2K2G3A, 29 June 2026)

CORE-8969

Investigated and resolved an issue where an order could be abandoned in the system while a payment was still captured by the payment gateway, leaving the customer charged with no corresponding live order. This ensures payment capture and order completion remain consistent.

Harden cart: drop qty ≤ 0 ticket types on add-to-cart (stop 0-qty line items persisting)

CORE-8979 (Implements CORE-8974)

Fixed an issue where ticket types with a quantity of zero were being persisted on bookings, resulting in spurious zero-quantity line items appearing on orders. The cart now correctly filters out any ticket types with zero or negative quantities before storing, so only genuinely purchased items are recorded. This does not affect search behaviour, which continues to return pricing for all available ticket types.