Hello WAL Development Team,
Thank you for reporting this. The behavior you’re seeing is expected in some scenarios because of how Outlook optimizes conversation view and handles add-in lifecycle events. When you switch between messages in the same conversation, Outlook often reuses the reading pane context for performance. This means the ItemChanged
event may not fire because the host doesn’t consider it a full context change. For certain item types (encrypted mail, calendar invites), the add-in may reload entirely instead of raising ItemChanged
.
Make sure your UI refresh logic runs on add-in initialization (using Office.onReady()
or Office.initialize()
) as well as in the ItemChanged
handler. This covers cases where the add-in reloads or the event doesn’t fire.
Check if SelectedItemsChanged
fits your scenario If you’re on Mailbox API 1.13 or later, this event can help in some cases where ItemChanged
falls short, especially in OWA or New Outlook. Use Office.context.roamingSettings
or similar to keep track of the last processed item so your add-in can restore the correct view after a reload.
There're some similar cases related to ItemChanged
, please check out:
- Outlook addin is not able to get updated context while pinned
- Office.context.mailbox.item does not update after ItemChanged event — still refers to the initial item
If you think this problem come from our developer team, please hesitate out in Office Dev Issues or Microsoft 365 Developer Platform
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Best regards,
Sin Dau