🚀 Overview

In Microsoft Outlook for Microsoft 365, “Actionable Messages” allow users to complete quick tasks (such as approving expenses or responding to surveys) directly within the email client using Adaptive Cards. However, a known synchronization issue occurs when a user opens an actionable message in a pop-out window.

If a user interacts with the message in that separate window—for instance, clicking an “Approve” button—the pop-out window correctly updates to show the new state (e.g., “Request Approved”). Despite this, the Outlook Reading Pane in the main application window may continue to display the original, stale version of the message. This creates a visual discrepancy where the main view does not automatically reflect the actions taken in the popped-out instance.

⚙️ Key Technical Details

The synchronization of the Outlook Reading Pane depends heavily on the configuration of the Adaptive Card payload and specific user interactions. The core technical components include:

• The autoInvokeAction Property: This property, when defined within the Adaptive Card payload, provides an HTTP service endpoint. Outlook uses this endpoint to fetch the most recent state of the message from the service provider.
• Payload Definition: Developers use the Microsoft Actionable Message Designer to include the autoInvokeAction property. If this property is missing, Outlook relies on cached data rather than fetching a fresh update from the server.
• State Persistence: Depending on the backend implementation of the HTTP service, the message state might be “global” (reflecting the cumulative actions of all recipients) or “local” (specific to the individual user).

📅 Refresh Scenarios and Resolutions

Whether the Reading Pane updates depends on which of the following scenarios applies to the message:

Scenario A: The Message Defines autoInvokeAction

🛡️ Behavior: If the property is present, the Reading Pane can be triggered to refresh via the following actions:

• Saving the Window: The recipient saves the message while in the pop-out window view.
• View Switching: The recipient clicks on a different email in the Reading Pane and then clicks back onto the actionable message. This “re-focusing” triggers an automatic refresh.

Tip for Admins: You can verify if a message contains this property by using the Actionable messages debugger for Outlook add-in.

Scenario B: The Message Does NOT Define autoInvokeAction

⚠️ Behavior: Without this property, Outlook will not automatically fetch updates from the service endpoint. Instead, it displays the most recent version of the card that was previously cached in that session. To force a refresh, the user must:

• Close the pop-out window, navigate to a different email in the main Reading Pane, and then return to the original message.
• Restart the Outlook client entirely and navigate back to the message.

📋 Impact

This issue primarily impacts user experience and workflow clarity. Because the Reading Pane does not update in real-time alongside the pop-out window, users may become confused or doubt whether their action was successfully processed.

• Help Desk Volume: Admins may receive tickets regarding “frozen” or “unresponsive” approval buttons if users rely on the Reading Pane to confirm their actions.
• Data Integrity Perception: If a user sees an “Approve” button in the Reading Pane after they have already approved the item in a pop-out, they may attempt to perform the action a second time, leading to potential duplicate submission errors from the backend service.
• Administrative Guidance: IT Admins should encourage developers of internal actionable messages to implement the autoInvokeAction property to ensure a more seamless synchronization experience for end-users.

Official Source: Read the full article on Microsoft.com