Message body returned by the Graph Call is not up to date on replies

[mikey8808]

In New outlook and OWA, when calling the route 'https://graph.microsoft.com/v1.0/users/{EMAIL}/messages/{RESTID}?$select=Body', the message body returned does not include the latest changes after sending the email quickly. This has regressed as it did not happen before.

Your Environment

• Host [Excel, Word, PowerPoint, etc.]: New Outlook / OWA
  *Microsoft Outlook Version:

New Outlook Version:
Microsoft Outlook Version: 1.2025.219.400 (Production)
Client Version: 20250221002.19
WebView2 Version: 133.0.3065.92 (Stable)
Session ID: eee6bad0-73a2-e84e-962a-79a2afea24b3

In OWA, this fails in previous earlier versions to 20250214004.16

Expected behavior

Calling the route https://graph.microsoft.com/v1.0/users/{EMAIL}/messages/{RESTID}?$select=Body' should return the entire message body.

Current behavior

When calling the route 'https://graph.microsoft.com/v1.0/users/{EMAIL}/messages/{RESTID}?$select=Body', the message body returned does not include the latest changes after sending the email quickly. Inconsistent behaviour between version mentioned for OWA and version in New Outlook. Works fine in win32 outlook and mac outlook.

Steps to reproduce

1. Sign into Outlook
2. Select an existing email in your Inbox, click the Reply All button, type something in the body and quickly send.

[mmanjaree-msft]

@mikey8808 This forum is limited to supporting office-js apis. For any MS API Graph specific queries and support, please explore options available at Microsoft Graph Dev Center | APIs and app development

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your interest in Office Add-ins!

[microsoft-github-policy-service]

This issue has been closed due to inactivity. Please comment if you still need assistance and we'll re-open the issue.