问题
Changes in OneNote client aren't immediately reflected in apigee. For example:
Renaming a section in OneNote client. Apigee shows the old name.
Adding a section and adding notes to that section in OneNote; these
aren't reflected in my app that uses the API. As seen below:
Is this a API call caching issue or a known OneNote issue? Whats the recommended way to resolve it? I'm using Superagent and wondering if its no-cache plugin would resolve this.
回答1:
If you add the following header to an API request it seems to reduce the amount of caching that happens.
FavorDataRecency: true
The trade off seems to be a larger overhead for the request and a greater likelihood of triggering throttling (429 errors).
The OneNote team could probably explain this more precisely.
回答2:
EDIT: This option is no longer supported.
Codeye is right - You can use
FavorDataRecency: true
To skip our index. However, the index is refreshed based on changes made to OneNote content, so the delay (if you choose to not use FavorDataRecency) shouldn't be more than a few minutes
来源：https://stackoverflow.com/questions/41172325/is-there-a-way-to-overcome-lag-between-changes-in-onenote-client-and-api-results