Reservations coming from Synxis are failing
Incident Report for Mews
Postmortem

Problem

On 2023-04-21, between 09:27 and 13:07 UTC, all incoming messages from Synxis stopped being accepted due to a code error in request authorization.

Action

• After detecting the issue, we reverted the Mews application to the previous version.
• At the same time, we contacted Synxis with a request to resend the missed reservations.

Causes

The main issue was that we didn't have automatic detection for this kind of incorrect code, as our test environment was configured differently to the production environment. This caused the incorrect code to not be triggered and found out.

Solutions

  1. The automatic detection for this kind of code is not feasible, so we will match our setup in all environments to the production one.
  2. We are adding base creation for all clients that will reflect the settings in production, to test against the correct setup and trigger the right parts of the code.
Posted May 25, 2023 - 14:19 CEST

Resolved
The issue was resolved, and new reservations are already coming through correctly.
We are in touch with Synxis about the recovery of all missed reservations.
Posted Apr 21, 2023 - 15:30 CEST
Identified
We have identified root cause of issue.
We are currently deploying revert.
We will contact Synxis to resend us all failed reservations, their modifications or cancellations.
Posted Apr 21, 2023 - 12:07 CEST
Investigating
We are currently investigating issue.
All reservations coming via Synxis are failing and are neither stored in queue.
Posted Apr 21, 2023 - 12:04 CEST
This incident affected: Marketplace.