What went wrong:
A change included in Thursday's release added new fields to capture terms and conditions acceptance on bookings made via the API. Due to a configuration error, these fields were not recognised by part of our internal booking system, which caused bookings to fail immediately, including bookings that didn't involve terms and conditions at all.
Who was affected:
Dublin customers booking through the JSON 2.1 API were unable to complete bookings during the impact window. Website and iSell bookings were not affected. No data was lost.
Resolution:
We reverted the release changes and bookings resumed immediately.
What we're doing to prevent this happening again:
We're improving our release validation so that any new field added to the booking process is checked and verified before deployment.
We're also fixing a gap in our error logging so that any future booking failures are recorded and visible straight away, rather than failing silently.
We are also reviewing our internal processes to ensure there are no gaps.