Recurrence is undefined for recurring instances

[lukesolar]

We have a problem with the Outlook versions starting from February 11, 2025. When used in conjunction with Exchange Server 2016 or higher. (See Microsoft 365 version log)

The same or a similar issue was already reported here some years ago, seems it was fixed but it's now happening again.

When opening an instance of a recurring meeting, the Office.context.mailbox.item.recurrence is "undefined". But it was working perfectly well before. This results in errors like "Cannot read properties of undefined (getAsync)" since we access this property like this:

// compose view
        Office.context.mailbox.item.recurrence.getAsync(function (asyncResult) {
                if (asyncResult.status === Office.AsyncResultStatus.Succeeded) {
                    let recurrence = asyncResult.value;
                    // proceed with other code
                } else {
                    // error
                }
            }
        );

This is resulting in errors such as cannot read properties of undefined (reading 'getAsync')

Your Environment

• Windows 11
• Exchanger Server 2016 or higher

Microsoft 365/Office Versions where the error occurs:

• Not working! 2408 Build 17928.20440
• Not working! 2412 Build 18324.20240
• Not working! 2411 Build ?
• Last known working version: 2408 Build 17928.20440

Expected behavior

Office.context.mailbox.item.recurrence should not be undefined, but contain recurrence info.

Current behavior

Office.context.mailbox.item.recurrence is undefined.

Steps to reproduce

• Create a basic Add-in and open a SidePanel in the compose view of the Calendar Items.
• Create a recurring event.
• Open an occurrence of the event (Do not open the entire series, for the entire series the recurrence object still populates).

// compose view
        Office.context.mailbox.item.recurrence.getAsync(function (asyncResult) {
                if (asyncResult.status === Office.AsyncResultStatus.Succeeded) {
                    let recurrence = asyncResult.value;
                    // proceed with other code
                } else {
                    // error
                }
            }
        );

Observe that Office.context.mailbox.item.recurrence is undefined.

Screenshots

Please help and support us, this is a commercial Add-in!

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• Office.context.mailbox.item.recurrence.getAsync throws error  #1312
• recurrenceAdapter.ts:13 Uncaught (in promise) TypeError: Cannot read property 'Recurrence' of null #1051
• Office.context.mailbox.item.(requiredAttendees|location) is undefined when creating a Meeting from an Email #5365
• Changing until-date in recurring meeting causes mailboxItem.recurrence.getAsync() to stop working due to unhandled exception #3125
• Office.context.mailbox.item.recurrence.SeriesTime end values are zero if recurrence started in the past #1978

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Solution 1:

Unfortunately, we are still investigating this issue. Please do use the Graph API as a workaround for getting the recurrence of the meeting till this is resolved: https://docs.microsoft.com/en-us/graph/outlook-schedule-recurring-events

Reference:

• Office.context.mailbox.item.recurrence.getAsync throws error  #1312 (comment)

Solution 2:

Hi, looks like there are multiple issues being talked about here, causing confusion. 1. recurrence.getAsync throws error / returns null - This issue has been fixed from our end on OWA. recurrence.getAsync() shouldn't be returning null anymore. We aren't able to reproduce this bug from our end any more. If you're in organizer mode, make sure you call recurrence.getAsync() and not item.recurrence. Please verify this on your end and let us know if you're still able to reproduce it.

Reference:

• Office.context.mailbox.item.recurrence.getAsync throws error  #1312 (comment)

Powered by issue-sentinel

[lukesolar]

Graph API is not available for accounts connected to Microsoft Exchange Server 2016. (I updated the environment infos)

[lukesolar]

Update: Customers reports this problem also exists in version 2411 (December 2024).