We have backfilled message threads for the reservations that were affected during this time window. You should now be able to retrieve the `thread_id` associated with a reservation using the Reservations API. Apologies for the inconvenience.
If you have any further queries related to this incident, please submit a ticket via the Partner Support Portal and our team will get back to you as soon as possible.
Posted Jul 13, 2023 - 09:22 PDT
Identified
We have identified an issue that caused reservations to be created without associated threads. This occurred between 10:15 PM and 11:29 PM on July 12th (PST), so notifications for reservations created during that time were sent with a null `thread_id` value.
We are actively working on creating threads for reservations that do not have them, and will update here afterwards.
Once this is done, you will be able to retrieve the `thread_id` value for a reservation using the Reservations API.