As of yesterday, it appears that the Onenote /pages endpoint is not working properly for my account. The data returned for the first two pages is recent, however all other pages and their respective HTML content links are last updated as of Feb 28th 2020. Additionally, some of the pages showing up as "last edited" on Feb 28th 2020 are pages that I know for a fact have not been edited for months (place holders, old projects, etc.)
I have described a similar problem before: here and here. Such a problem was also described by another recently. Upon resolution of those issues, Manjusha stated that it was because of a "bad machine cluster causing jobs to get stuck" and therefore delaying updates. While this suffices to explain the delay, the inaccurate edit dates on page does not seem to be accounted for.
Any updates on the issue or insight into what is happening would be greatly appreciated.
UPDATE Mar. 5th 2020: Using the graph explorer, I can see that the pages endpoint is returning the same out-date response again and again. Basically, it is frozen in that state from what I can see.
I'm sorry to say this, especially at such a stressful time. However, the reliability of the pages endpoint has been up in the air for months. Working sometimes, not working at others. Personally, this has forced me to rebuild my personal programs so they do not rely on OneNote and reconsider using OneNote in professional settings where new pages are being made regularly. The sum total of this has been to cease development and usage of the OneNote API. Just a bit of feedback. I know your team works hard and these issues are complex - I hope this clears up for you soon.
Can you send the request-id header from the response and your request timestamp? Thanks!
Related
I use Google API to get a JSON result of my own YouTube channel videos.
The URL has not changed, but suddenly, Google returns the JSON only with order=relevant instead of order by date.
https://www.googleapis.com/youtube/v3/search?part=snippet&channelId=UCqEcEGQ0sG89j7ZhOdgFOyg&maxResults=24&order=date&type=video&videoType=any&key=<key>
The first result returned will be a 2 year old video instead of yesterday's one.
This call did work 'till last week (week 11 2016)
From this thread, it seems it is a bug and that the YouTube team is aware of it. A Google employee responded 3 days ago with:
YouTube is aware the search/sorting functions aren't working as
expected – this is temporary and part of our efforts to better
respond, review and remove graphic, violative content from YouTube.
Thanks for your patience while we work through this. Will update this
thread when these features are working normally again, feel free to
subscribe for updates.
You can subscribe to the thread for faster updates.
In our app we use foursquare search endpoint to get nearby venues.
Everything was working good until yesterday, but now there is one strange thing, after few refreshes api returns less venues, if i refresh it few times, then normal result is back.
you can check API behaviour by entering this URL and refreshing it few times
#foursquareAPI tweeted as following:
Some developers might be experiencing issues with venues/search?intent=browse. We're currently investigating!
12:37 AM - 22 Sep 2015
I think your problem is also perhaps related to this.
I have an iOS app that has been fetching the user's Facebook status updates and location checkins using "/me/posts" for several months. After today's "breaking changes" update, "/me/posts" only returns recent "Like"s. It looks like "/me/statuses" and "/me/checkins" are the new proper places to check for these things. I guess that makes sense, but I saw no documentation anywhere describing these changes or saying that they would happen today. The original documentation about what is specifically returned from the graph API also seems pretty slim.
So my questions are: is this an official change to the API? Where was it specified? Where should I look so I can stay on top of these things and not have my app break for hundreds of users?
Perhaps more importantly: are "/me/statuses" and "/me/checkins" the new proper ways to get this information? Or is there something else?
Always good to keep a (sharp) eye on the Developer Roadmap. These types of changes happen often, but FB usually does a good job of calling them out ahead of time. You've answered your own question as far as whether or not it's an "official" change - you're seeing it in the wild - insofar as how Facebook works, it's official.
Try using the Graph API Explorer. It could be an access token issue.
FYI: I see a similar issue with my application, and I am able retrieve the posts only when I use the Graph API Explorer and the token I get from there.
Update: I found where some of the problems lived. In the app profile in Facebook, pick "Edit Settings" and then go to "Advanced" where you'll see a section called "Migrations". This is mostly switches to show compatibility for various "breaking changes" updates, but it also includes an option for "Include Checkins with Statuses".
Now I know where to look, things are making a bit more sense.
I've got a content experiment running in Google Analytics and it isn't showing any visitors. The code is validating correctly and appears to be functioning correctly if I test it.
I've used parameterised versions of the same page (?v=1, ?v=2, ...) for the different variations.
It also may be because the experiment is on a search page which receives a parameter of what is being searched on in the URL.
Anyone got any experience with these problems yet?
It seems to take a few hours for my data to start showing up. So depending on how impatient you are it may just take more time.
I also had a problem since I had Enable Demographics and Interest Reports turned on (Question that might help)
Is anyone else experiencing problems with the Bing helper in Microsoft.Web.Helpers?
The Bing.AdvancedSearchBox helper method tried to load the following javascript file but throws a 404 error. The script is http://www.bing.com/bootstrap.js
Has anyone else experience the same problem? So far there has not been any updates to the microsoft-web-helpers package in Nuget. Any information is greatly appreciated.
Thanks,
Diego.
UPDATE 5/1/2011
I found the following official statement...
I wonder when Micorsoft will release an update to Microsoft.Web.Helper to remove the deprecated functionality.
Note: Bing team at Microsoft announced that they will be shutting down siteowner service on April 4th. This will prevent you to use the AdvancedSearchBox feature of Bing on your website/blog or web applications. Here is the quote from Bing's official blog:
As of April 4th, 2011 we will discontinue support for the bing.com/siteowner functionality. If you continue to leverage the feature after this date (April 4th, 2011), users who attempt to query in the search box will be redirected to a 404 page. This means that you will need to move to the Bing API in order to continue to receive web or site search results from us. We have decided to take this step for two reasons.
First, the tool has not been getting a lot of use and while we have some very loyal customers on it, we believe we can provide you better alternatives in the future as we free up resources.
Second, the functionality available through bing.com/siteowner can be replicated with the Bing search API and so it feels a bit redundant.
As has become customary, we will give you a window to migrate off and ask us any questions you may have about this change. We will also provide reminders as we get closer to April 4th. Thank you so much for your support.
It looks like something has changed on the bing servers and this script no longer exists.