We have no options for mitigating this in our own Outlook Add-in and Microsoft has acknowledged the issue and put it in their backlog. See: https://github.com/OfficeDev/office-js/issues/2677/
Microsoft has not provided a timeline for a resolution but we will keep you updated on progress.
Current workarounds include:
- Postpone updating to Mac Outlook client version 16.62
- Use the Outlook Web Application
- Switch to the old Outlook Client for Mac temporarily. In the client, this is done by navigating to the top left corner and clicking on "Outlook", and then removing the tick from "New Outlook".
Jun 30, 15:44 CEST
Current workarounds for this issue:
- Postpone updating to Mac Outlook client version 16.62
- Use Outlook Web Application
- Switch to old Outlook Client for Mac temporarily. In the client, this is done by navigating to the top left corner and clicking on "Outlook", and then removing the tick from "New Outlook".
Jun 24, 14:29 CEST
Jun 23, 10:47 CEST
About This Site
The AskCody Statuspage is the main communication channel for all issues affecting the operational status of AskCody Products. This includes both our infrastructure and services, referred to as components. These are divided into Europe and North America based on the two cloud platforms (onaskcody.com and goaskcody.com).
Component status definition:
Operational: The default status for all components, 100% available and operation for all customers.
Under Maintenance: Used for scheduled maintenance. This is informed in advanced based on our SLA specification.
Degraded Performance: Component is affected by slow response time that affects user experience but does not make that component unusable. Does not affect downtime.
Outage: Partial Outages only affect a subset of users or product components. Affect the up-time calculation 30%.
Major Outage: Affect 100% of the people using the component/product thus affecting up-time calculation with 100%