Replies: 1 comment 2 replies
-
Hey @nicognaW You're right, the reason for this is concurrency. Lock might be one of the ways to fix it, but we must explore other potential solutions to this as well. Thank you for bringing light to this. 🙏 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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?
Beta Was this translation helpful? Give feedback.
All reactions