🧪 Experimental KB — Official knowledge hub: community.kaptio.com

Confirmation status not updating to 'Unconfirmed Amendment' when changing itinerary dates

When using the 'Change Start Date' function on an itinerary, confirmed services were not updating their confirmation status to 'Unconfirmed Amendment' as expected. The services remained showing as 'Co

confirmation-status change-start-date unconfirmed-amendment date-changes itinerary-builder

Problem

When using the ā€˜Change Start Date’ function on an itinerary, confirmed services were not updating their confirmation status to ā€˜Unconfirmed Amendment’ as expected. The services remained showing as ā€˜Confirmed’ even after dates were changed.

What We Found

This was a bug in Kaptio core (tracked as KT-8741). The ā€˜Change Start Date’ function on the itinerary was not triggering the expected confirmation status update to ā€˜Unconfirmed Amendment’ for confirmed services when travel dates were modified.

Solution

  1. Identified this as a Kaptio core bug and created internal ticket KT-8741
  2. Provided workaround: Use ā€˜Bulk Shift Dates’ in the itinerary builder instead of the ā€˜Change Start Date’ function
  3. The bug has since been fixed in the Kaptio platform - customer confirmed the issue is now resolved and status shows ā€˜Unconfirmed Amendment’ correctly

Notes

  • The workaround (bulk shift dates in builder) only applies when changing all travel dates, not individual service dates
  • Customer initially reported the issue also occurred when changing individual service dates, but support could not reproduce this in testing
  • This fix was deployed as part of a Kaptio core release - the exact release version was not specified in the ticket

Warnings

āš ļø If a customer reports this issue, first verify they are on the latest Kaptio release as this bug has been fixed


Source: KHELP-10197

Was this article helpful?