[CAL-863] No available users found error on confirming booking for an open slot
Found a bug? Please fill out the sections below. 👍
Issue Summary
I have not replicated this personally, but I have had different users report this error on more than occasion.
When confirming an individual booking [not a team page], some users have seen this error: "Could not book the meeting. No available users found."

by any chance, is your event-type link called "book"? thats an ongoing issue we are fixing right now
by any chance, is your event-type link called "book"? thats an ongoing issue we are fixing right now
It isn't, it's called bau
weird...
we're putting in a lot of work right now in the booking page, maybe a team member knows more. you said you cant reproduce this. any idea what this could cause?
Same error for me, with 2 different contacts (without account in cal.com).
upgraded to urgent. we need to get rid of this error message all-together and get to the bottom of this
@ChipWolf Is this slot made available through a date override?
date override?
@milospuac yes for me :+1:
This is also impacting users trying to book through my cal.com link. The slots are not available through date overrides, just normal, open slots.
I think that the "No available users found." error message come from this line.
Why this line
const { busy: bufferedBusyTimes, workingHours } = await getUserAvailability(
don't get dateOverrides variable? :thinking:
@emrysal
@ChipWolf Is this slot made available through a date override?
Yes
@ChipWolf @PeerRich Question: do you have a Merge Request in work in progres to share about this is issue ?
not yet, i believe different issues cause the same (bad) error message of "No available users found"
Some news about this issue?
I'm stuck, waiting for this bug to be fixed and I don't know if it's better if I try to fix this bug myself or if I should go to https://calendly.com/ or https://savvycal.com 🤔
hey, we are actively working on this, it seems to be some sort of user error because it doenst show up for each user.
I understand this is super annoying which is why it has an urgent flag
lemme also give it a bounty
/bounty 1000
💎 $1,000.00 bounty created by PeerRich
👉 To claim this bounty, submit a pull request that includes the text /claim #6622 somewhere in its body
📝 To receive payouts, join Algora and complete the relevant onboarding steps
💵 Payment arrives in your account 2-5 days after the bounty is rewarded
💯 You keep 100% of the bounty award
🙏 Thank you for contributing to calcom/cal.com!
@stephane-klein I cannot reproduce this on your link

ok i was able to reproduce it on this link:

i think i know why: for that link you have a different availability that has no available dates:

@PeerRich Hi everyone!
@JeroenReumkens shared this issue with me and I have found a fix for it. I'm doing some testing now and once done I'll open a PR for you to review!
💡 mischarouleaux submitted a pull request that claims the bounty 👉 To accept and/or reward this claim, visit your org dashboard on Algora
@PeerRich @JeroenReumkens Just submitted the PR, feel free to add people to review it!
I am trying to track progress on this issue across a couple of different threads, so I apologize if this is the wrong place for this comment, but just wanted to register that the error is popping up on my account even though I am not actively making use of date overrides.
can you check if you have availability?
Yeah, for me this is happening on normal calendar bookings with completely available dates, no overrides. Started happening about 1.5/2 weeks ago, or at least that's when a client of mine first reported it to me. EDIT-- For what it's worth, I read somewhere during my research through this repo that this error might be being shown accidentally/in cases where the underlying cause has nothing to do with availability.
Same issue here, prospective clients notified me about it. Definitely an urgent issue.
Same issue, although it also sometimes shows up as: Could not book the meeting. invalid_type in 'api_key': Required... Weird because everything was working fine as of yesterday
I updated everything and rebuilt the calcom docker. The availability issue and the "API_key" issue resolved itself.