I only have 15-20 messages in my inbox for June 20. But when I run a search query for that day
https://graph.microsoft.com/v1.0/me/mailFolders/inbox/messages?$search=" received = 2019/06/20"&$select=from,id&$top=1000
I am seeing that the results are repeating, meaning the same message id keeps circling back (think its an infinitely) and the results take several seconds to return.
I am even able to reproduce that with Graph explorer. It doesn't seem to happen for other days in my inbox. I think I have come across some bug in the system but unclear what exactly it is.
Anyone know what it is?
This issue is now fixed. Can you pls try again?
Related
My organisation is facing issues with running out of slots allocated Monday morning running GCP queries and we suspect this is partially due to the number of autofresh connected sheets that have been set and forgotten. We may need to ask Google to get a list of all the autofresh queries and the creators, but before we get to that, is there a way for users to check themselves first ?(Personally I have got a few queries set up as autofresh last year but now I can't remember what they are, let alone cancelling them. )
Thanks in advance.
Hopefully I'm not the only one having this issues. When I request meeting time suggestions, which includes an attendee and time constraints, I get a response of 5 meeting suggestions. The issues is, that the slots have a gap in time, some times several hours. However, all attendees have that gap time as free; additionally, if I change the duration or increment the time one direction or another, the missing time slots show up. On a related note, is there a way to request more than 5 meeting time suggestions?
I think the perceived "gap" here is because you're expecting the meeting suggestions to be returned in chronological order, which is not the case. The FindMeetingTimes API tries to infer the user's preferred meeting times based on their past meetings, and the meeting suggestions are returned sorted by what the API thinks would be the most preferred. It's most likely that the "missing" time slots are lower down in the ranking, and you're not seeing them because you are only getting the default 5 results back.
You can request more results by including the maxCandidates parameter in your request body. See https://developer.microsoft.com/en-us/graph/docs/api-reference/v1.0/api/user_findmeetingtimes#request-body for details.
I have a YouTube API Key, and I was testing it out when I started watching my [requests] through the dashboard?project=myproject-111111&duration=PT1H
The issue is this. I stopped using the key about 15 minutes ago, and that blasted thing is STILL counting. Since I stopped using it, it has gone from
9,875 -to- 39,978 (And still counting)
Why would this be still counting for? The key is NOT being used, but its counting.
You are allowed 1 million requests per 24 hour day. And at this rate, I will be there in no time flat.
I have tried to find an active Forum for the YouTube API, and there is none. The only ones I found had their last post in 2012 and 2014.
Any idea's why this thing is still counting? (46,333)
Updated 10:47 pm EST: On the [Quotas] page. It is over 300,000+ and counting. This is a blasted joke. I reported it in as a bug, but the bug reporting page, is so full of SPAM, that it makes you wonder on rather they are going to check it regularly or not.
Updated 10:51 pm EST: It finally stopped. Conflicting count returns are coming in from the different pages.
118,762 on the dashboard
415,489 on the YouTube Quotas page.
I went to the YouTube Developers Twitter page and tweeted to them about the issue, and am awaiting a reply back.
I will post here, once I get a reply back.
Is this a BUG?
Or, do other issue?
CodingEE
This is something that I was looking at. As quota is eaten up by api calls that the site is not actually making.
This is unfortunately something for Google to fix. I did send a request to look into it, but no reply.
The cause is "BOTS". They will search, index and run the page affectively to index and rate it. As such, the will incur api usage.
This can be reduced in a few ways.
1: If in testing stage, and you do not use the online version too often apart from testing updates to code, then you can remove the api key from the code while not testing.
2: If it is live and running, but you wish to stop the bots eating the quota, then in your Google dashboard, block the bots.
This will however stop indexing. So I would recommend "trying" to limit them and how often they inex.
Aside from that, we need to get Google to (if possible) not use quota for bots.
I am having issues with Kimono Labs. Every scrape I run will run indefinitely without throwing an error or completing. Occasionally, the scrapes will randomly start working days in the future without any changes on my behalf - only to fail a few days later. I love Kimono because it is so easy to integrate with Google Sheets for friends to alter the data, but this has become problematic. There doesn't seems to be any related help in the Kimono help data for an issue such as this.
One of my scrapes is not behind a paywall and the other is. One is set to run daily and the one behind the paywall is set to run hourly.
What steps can I take to troubleshoot this error and get the ball rolling again?
I had a very simple API doing the exact same thing for weeks!
I'm only using a free account so I didn't have any support but I ended up sending a bug report at https://www.kimonolabs.com/support .
Strangely enough, the very next day, the API started working normally again (and has ever since). I assume they looked into it and fixed whatever was stopping my crawl from completing.
The following YouTube Analytics query is suddenly failing for me (has worked for the past couple of weeks):
https://www.googleapis.com/youtube/analytics/v1/reports?ids=channel==[my channel id]&start-date=2010-10-27&end-date=2010-10-30&metrics=views&dimensions=day,insightTrafficSourceType&sort=day&prettyPrint=false
The error:
{"error":{"errors":[{"domain":"global","reason":"badRequest","message":"Invalid query. Query did not conform to the expectations."}],"code":400,"message":"Invalid query. Query did not conform to the expectations."}}
Appears to be related to the "insightTrafficSourceType" dimension as the query succeeds if I only use the "day" dimension. This also fails if I use the "insightPlaybackLocationType" dimensions.
Did something change with the API? I would like to use both of these dimensions in my reports.
Any help would be appreciated.
Thanks,
J
Stack Overflow is not a good place to report bugs; I've opened a public issue tracker bug report for this problem at https://code.google.com/p/gdata-issues/issues/detail?id=3963, and I'd recommend "Star"ing that to keep updated on the status of the issue.
Also see http://apiblog.youtube.com/2012/09/the-youtube-api-on-stack-overflow.html for info on creating bug reports/feature requests yourself.