Forum Discussion
Introducing Scheduling poll in Outlook!
Nick Nigro Sullivan910 ph_ly
Yes, this is a known issue, i.e. when a user tries to use FindTime add-in to schedule a poll, they may run into this error/issue. FindTime engineering team is looking into it for resolution. A service incident (EX521435) has been published for impacted tenants, see below for details, if you haven't seen it yet in your M365 Admin center. Workaround is to use Scheduling poll feature in OWA.Update: This issue has been fixed.
EX521435: Exchange Online - Users can't schedule events in the Outlook desktop app using the FindTime add-inImpacted users get an error that states, "Sorry! FindTime could not load due to an unexpected error. Please try again." or "Sorry, we can't load the add-in". While we're working to remediate impact, affected users with access to Outlook on the web can use the Scheduling Poll feature to schedule meetings. See: Scheduling Poll articles - Microsoft Support for more info and share these with your users.
Current status: We're reviewing additional information, including the status of authentication components which facilitate user access to the add-in, conditional access policies related to FindTime add-in subscriptions and collecting additional service logs for further insight into how impact manifests to assist our investigation.
You can follow the steps below to remove FindTime from Outlook Windows Ribbon.
File | Options |
- Select Customize Ribbon
- In the third column, Customized the Classic Ribbon, make sure "Main Tabs is selected.
- Under Main Tabs, expand Home (Mail).
- Click on FindTime.
- Click on the Remove button.
- Press Ok.
- You are not deleting the app but removing it from the ribbon. You can add it back anytime.
If you find this information helpful, please mark it as the best answer to assist others with the same question.
/Teresa
#traccreations.
Yes, I knew the steps to remove it from the ribbon. When I attempted to remove it using that method, the "Remove" button was greyed out, so I couldn't actually remove it.
A few days later, I tried again, and was able to remove it. Don't know why or how things were different. But they were.