Solved situation with Mews Booking Engine

Problem

A bug affecting multi-property booking engines was introduced as part of a deployment on the Booking Engine API. The issue caused errors for multi-property configurations while single-property booking engines continued to function normally. Because the error rate remained low overall, the problem did not trigger automated alerts and was only discovered when customers reported the issue.

Action

Once the incident was raised, engineers investigated the issue and quickly identified the defect in the recently refactored asynchronous endpoint. A fix was implemented, reviewed, and approved within minutes. Deployment of the fix took significantly longer due to unrelated build-pipeline congestion, but the corrected version was eventually deployed to production at 00:50 UTC.

Causes

• As part of adding new booking engine functionality, the endpoint was refactored to be fully asynchronous.
• This refactor unintentionally introduced a bug that affected multi-property booking engines.

Solutions

​The problematic asynchronous refactor was corrected, and the fix was deployed during the incident.