Reservation Group Creation Issue

Update timeline

1. identified Feb 03, 2026, 02:10 PM UTC

   We've identified an issue affecting how reservation groups are created: - Availability blocks using "All in one group" pickup distribution are currently failing with a validation error - For all other reservation types, new reservation groups are being created incorrectly instead of adding reservations to existing groups when appropriate We've identified the root cause and are currently rolling back the change that introduced this issue.

2. resolved Feb 03, 2026, 02:35 PM UTC

   We have successfully rolled back the change and confirmed that reservation groups are now being created correctly. A page reload is required to apply the changes. Note: Reservations created during the incident may still be in separate reservation groups instead of the intended shared group. Please review reservations created between 10:55 UTC and 14:23 UTC for any regrouping needs.

3. postmortem Feb 19, 2026, 08:56 AM UTC

   ## Problem On February 3, 2026, properties using Mews Operations were unable to add new reservations to availability blocks configured to accept only a single booking group. Any attempt to do so resulted in an error. As a result, staff were unable to create new reservations within those availability blocks for the duration of the incident. In addition, approximately 2,000 reservations that should have been added to an existing booking group were instead incorrectly placed into separate, newly created groups. ## Action Our team was notified of the issue and began investigating immediately. We identified the source of the problem, verified a fix on our test environment, and restored Mews Operations to the previous working version on production. The issue was fully resolved by 15:03 UTC, with error rates returning to zero shortly after. ## Causes The incident was triggered by a software update released earlier that day. The update inadvertently caused Mews Operations to stop correctly identifying which booking group a new reservation belonged to. As a result, the system treated each new reservation as belonging to a brand new group, which conflicted with the single-group rule set on those availability blocks. ## Solutions We restored the previous working version of Mews Operations to immediately stop the impact. A targeted fix addressing the underlying cause has since been deployed. We are also introducing additional automated checks to this area of the system to prevent similar issues from reaching production in the future.