Unable to reshedule meeting

Hi ​@WernerK,

Hmm… that’s not good! I just tried reproducing on my end on a 1:1 event, but wasn’t able to reproduce the same issue. Can you tell me a bit more about your configuration including browser and what type of event?

Thanks!

I‘m using safari on iPads and on MacBooks (the newest versions).

BTW: when I‘m using the iOS App, I can change date/time, but I‘m unable to change the place to change from an address to a zoom meeting

Hi ​@WernerK, I can chime in here. We have been working on a known bug and just recently deployed a fix, within the past few hours.  I can’t say for certain without looking at your screen but it sounds like this was the same issue that was affecting you. Please try this again and let us know how it goes. Just to make sure we side step any other hiccups please sign out and sign back in. If you are still having issues please clear out your cookies and refresh your page. If you are still having issues with this workflow, let us know and I’ll elevate this ticket so you can get some one-on-one help with Support. 

Hi ​@Sean Marlin 

still same behavior. 

I tried a little bit

I have meeting-types where I can do a reshedule. With some I can’t.

I have created a new meeting-type. Rescheduling is working. As soon as I configure more durations (30’, 45’, 60’) new created meetings are not possible to reschedule.

When I delete the additional times (45’, 60’) resheduling is possible again.

Hope this helps to reproduce,

bye werner
 

Hey ​@WernerK, we are having a some trouble replicating this issue on our end. We are a little limited here but we suspect this is an issue either with some event settings or your connected calendar. I think this is a case where support@calendly.com would be a better option. They can troubleshoot your issues live and get you a quicker solution. You can drop the url of this conversation in your email to help them narrow the issue quicker. Best of luck!

Hi again ​@WernerK. After a bit more digging, I was just able to reproduce what you’re seeing and have sent it to our product team. Such a strange issue!