Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreKeep your Zoom app up to date to access the latest features.
Download Center Download the Zoom appDownload hi-res images and animations to elevate your next Zoom meeting.
Browse Backgrounds Zoom Virtual BackgroundsEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI Companion2024-06-10 01:48 AM
I have Ghostery ad blocker installed and have had it for a few years now. Scheduling meetings with Zoom Chrome Extension has worked fine until early June 2024.
Now I click "Make It A Zoom Meeting" in the calendar event editing page and I get this error message:
"calendar.google.com says / Schedule meeting failed. Please try again".
Switching off Ghostery entirely (eg for every site) fixes it, but obviously I don't want to switch off my ad blocker for every site!
Trusting zoom.us and calendar.google.com sites in Ghostery doesn't fix it.
Thoughts as to what is going on? Is there a new site which needs whitelisting or is the Scheduling extension doing something it shouldn't be...?
Solved! Go to Solution.
2024-06-20 08:09 AM
Hi @bxr @shawbridge thank you for posting in the Zoom Community.
Our engineering team has let me know that this issue should be fixed now as this was a Google-wide outage. Please verify that you are no longer experiencing this issue at your earliest convenience.
Thank you!
2024-06-17 04:42 PM
I have exactly the same problem. It also started in the last two or three weeks.
2024-06-20 08:09 AM
Hi @bxr @shawbridge thank you for posting in the Zoom Community.
Our engineering team has let me know that this issue should be fixed now as this was a Google-wide outage. Please verify that you are no longer experiencing this issue at your earliest convenience.
Thank you!
2024-06-20 01:17 PM
Thanks Carla - yes after restarting Chrome a couple of days ago this functionality now works again. Thanks!