Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
10,592 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hahaha
OneNote graph API results lag behind current state
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 57.00000000000001%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMW%3C/text%3E%3C/svg%3E)
Mark Ward
15
Reputation points
I am calling the OneNote Graph API to list the pages in a section. The pages returned are not in the current state of the section. The OneNote desktop application on two different computers displays the current state of the section. The Graph API is returning old information. It takes over ten minutes or a certain action before returning current results. I am using Graph Explorer and JavaScript to call the API. The OneNote desktop clients display changes within a short time. It seems that the OneNote desktop app can query more current results, and the Graph API is limited to cached data.
Is this a case of eventual consistency?
These are descriptions of the API lagging results
I have a section with nine pages in it.
The Graph Explorer, JavaScript app, and OneNote app display all nine pages. In OneNote I deleted eight pages. A different computer with OneNote desktop app soon reflected this change. The OneNote Graph API continued to return the nine pages. The Graph API returned the nine pages for about 30 minutes. Eventually, the Graph API returned the current status of the section.
While awaiting the Graph API to return one page for the section, I decided to create a page using the Graph API. After creating the page, both OneNote desktop applications were updated and showed the newly added page. The Graph API continued to return the previous state. It took over ten minutes for the Graph API to return the newly added page.
Microsoft Graph
Office Development
Office Development
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Development: The process of researching, productizing, and refining new or existing technologies.
3,489 questions
{count} votes
-
Mark Ward 15 Reputation points
2023-01-26T19:29:04.2833333+00:00 I have just encountered a situation where the Graph API returned current results and then shortly after returned old results.
From the Graph API I created a new page in a section. Shortly after, I saw two OneNote desktop apps update with the newly added page. In my JavaScript client, I issued a new pages call for the section, and the API returned the current section page result. I then checked the JavaScript client on a mobile device, and the Graph API returned old results. I checked Graph Explorer, and it returned old results. I then tried the first JavaScript client, which received old results, losing the current state.
Five minutes later, the API response contains the current state on all devices.
Sign in to comment