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
- Identified this as a Kaptio core bug and created internal ticket KT-8741
- Provided workaround: Use āBulk Shift Datesā in the itinerary builder instead of the āChange Start Dateā function
- 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