Forum Discussion
Customers see an error message when they create a booking
Only a few minutes ago (2024-02-27 11:00) I noticed that when customers make bookings, they receive an error message and are asked to try again.
However, the booking is made in the Bookings calendar, meaning that when the customer tries again, they cannot attempt to book the same time, as it is now booked for them.
The customer receives no email confirmation of the booking.
The error message is something like "This booking could not be made, please try again". I have added a screenshot of the Finnish language error below.
Does anyone know if this situation is being addressed by MS?
For us, the issue seems to be solved as of today.
This is a message I got as a response to my support ticket:
Regarding your case, upon checking, there were a service degradation regarding the same issue you have. However, it was already resolved as well last February 26, 2024. With that, we need to give a propagation time of at least 7 days before the resolution takes effect for the entire Microsoft Community.
ptstockley I experience the same problem on our website (located in Denmark)... I will follow this discussion.
- We are seeing this same issue as well. Located in Finland too.
- Same problem here! Please fix asap 🙂
- Currently, this issue is causing our customers to attempt registration multiple times. Although they receive an error message each time, the reservation is processed successfully. For instance, we had one individual make reservations around 10 times consecutively. Our calendar is getting overbooked because of this issue 😕
- We are also getting this same error. But not on all bookings pages. For testing I created a new one and booking works fine, but another one created by a colleague gives this error.
Also in Finland if it makes any difference.
Babu_AlagarsamyMicrosoft
Can you please check if this is still happening?For us, the issue seems to be solved as of today.
This is a message I got as a response to my support ticket:
Regarding your case, upon checking, there were a service degradation regarding the same issue you have. However, it was already resolved as well last February 26, 2024. With that, we need to give a propagation time of at least 7 days before the resolution takes effect for the entire Microsoft Community.
- For us, this problem seems to be solved.
