Error when trying to add bookings

[sausin]

Found a bug? Please fill out the sections below. 👍

Issue Summary

An event has been setup with specific available hours and duration. When trying to add a booking, an error happens (pretty much randomly) with below message:

Steps to Reproduce

1. Went to booking page
2. Clicked on available slot
3. Entered the email and name
4. Attempted to book by pressing confirm
5. Booking fails (and XHR request errors with 400)

This should be relatively straightforward process and has been working smoothly until recently.

Actual Results

• Booking should go through without any issue

Expected Results

• Getting the error message as above

Technical details

• Not sure what the issue is. I have tried to have the booking location as MS Teams as well as Cal.com Video, but neither seem to work. Some people have been able to book the event on the other specified days in availability

Evidence

• A new event was created with an event duration and availability. Video of the error happening is here

[dosubot]

The error message "Could not book the meeting. EventType cannot be booked at this time" suggests a few potential issues that could be causing your booking failures. Here are some targeted areas to investigate:

1. Availability and Scheduling Constraints: Ensure the booking time is within the event type's defined availability, including checking for any restrictions on event length, booking limits, or specific scheduling types like Round Robin.

2. Calendar Conflicts: Verify there are no conflicts with existing events in the host's calendar that could prevent booking.

3. Technical Issues: Consider any possible bugs or technical problems, especially if the issue appears randomly. This could involve issues with database queries, external service integrations, or application logic.

4. Detailed Logging: Review application logs for any error patterns or specific messages that could indicate the root cause. The handleNewBooking.ts file, for example, should log detailed information about the booking process and any errors encountered.

5. Similar Issues: Look into similar issues reported by others, as they might provide clues or solutions. For instance, database credential problems or incorrect settings related to event intervals have been known to cause booking errors.

To move forward, it would be beneficial to gather more specific details about the error, such as browser console messages or server-side logs, which could offer more insight into what's happening.

Details

Sources

• [CAL-3321] better error when API is trying to book event type that has custom questions
• [CAL-2238] "Could not book the meeting." - Consistent error with any date and time
• But for 1 hour event time
• [CAL-704] Availability cannot span past midnight
• packages/features/bookings/lib/handleNewBooking.ts
• apps/web/pages/api/book/instant-event.ts
• packages/prisma/migrations/20231113202947_add_ical_columns_to_booking/migration.sql
• packages/prisma/migrations/20221129125935_add_metadata_to_booking/migration.sql
• packages/lib/checkRateLimitAndThrowError.ts
• apps/web/playwright/booking-limits.e2e.ts
• packages/features/bookings/lib/handleNewBooking/test/booking-limits.test.ts
• packages/trpc/server/routers/viewer/slots/util.ts
• packages/features/bookings/lib/handleNewBooking/test/team-bookings/collective-scheduling.test.ts
• packages/features/bookings/lib/handleNewBooking/test/fresh-booking.test.ts
• packages/core/getUserAvailability.ts
• packages/lib/slots.ts
• packages/features/bookings/lib/handleNewBooking/test/date-overrides.test.ts
• packages/features/bookings/lib/handleNewRecurringBooking.ts
• packages/features/bookings/lib/handleNewBooking/test/recurring-event.test.ts
• packages/trpc/server/routers/viewer/bookings/confirm.handler.ts

About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.