Long delay between save in Word Web and change in driveItem resource

[ErnstScheithauer]

Hello everyone,

we have found the following issue in testing our calls to the graph api:

• There is a document stored in SharePoint Online and it is being edited by a user
• The Word Web App saves the document - status says "saved" in the header bar
• The user switches to our application and clicks a button to continue
• Our application accesses the driveItem resource and downloads the content via the graph api
  • However, the latest save is not represented there for a variable timeframe from some seconds to more than a minute

It is important to use the latest version (and Word said "saved") so no user would understand that he has to wait for more than a minute to use the latest version.

• Is this by design?
• Is there a way to mitigate this?

Best regards,

Ernst

[#2]

FYI: According to MSFT-Support this is by design in Office Online, when the document stays open and there is an automatic background save (probably performance optimization to reduce load on SharePoint Online).
Only when closing (or refreshing) the browser an explicit and immediate save is performed to SharePoint.