Submitting the same time slot with multiple seats concurrently creates 2 bookings

[nicognaW]

I used a bash script to call https://cal.com/api/book/event to book the same time slot with 2 seats concurrently, caused 2 bookings instead of one containing 2 seat references created.

This caused 2 links created for daily video, users would usually like 2 seats to attend the same meeting, so this does not seem like a predicted behavior for me.

Maybe adding a unique constraint to the booking model or a lock could fix this?