As of this week I am suddenly getting gateway timeout from Graph when my mail search finds no results.
I am using a query like this one:
https://graph.microsoft.com/v1.0/users/shared#notreal.com/mailFolders/AllItems/messages?$search="participants:some.person#fake.com"&$select=from,subject,HasAttachments,Id,SentDateTime&$top=100
This is a Graph query which requests up to 100 emails from the Office 365 mailbox of shared#notreal.com where the sender or receiver includes some.person#fake.com. shared#notreal.com is a mailbox that is shared with the account making the call.
My app is authenticated with the oauth2 authentication code flow and has been granted all necessary permissions.
This has been working for about a year. But starting a few days ago, this query only succeeds if results are found. When no results are found, the query takes 30 seconds, Graph returns UnknownError and the response is 504 with reasonphrase Gateway Timeout.
It seems as though something has changed in the Graph API - or perhaps in the Office 365 API, but I can't find any mention of it anywhere.
Microsoft specifically directs questions about the Graph API to stackoverflow, so here I am. I hope the right people are reading.
Why has this suddenly started happening and how can I fix it?
Update: there are now numerous reports of this issue, confirming that it's at Microsoft's end.
Github issue
We saw this question and were actively investigating this kast week. With July 4th long weekend I hadn't got back to this thread until now.
This issue has been resolved on the back end of the service and you should not be seeing this issue anymore.
Thank you so much for sharing the service issue here.
This issue seems to be resolved on our end now.
Related
I am using Twilio's Verify API for authenticating my users through email and SMS by sending them an OTP.
So here are the observations and current situation.
SMS OTPs are almost instantly delivered
Email OTPs are sometimes instantly delivered and sometimes it takes 2 to 3 minutes.
There is no pattern in the slowness of Email OTPs
Talked to customer support but they failed to identify the root cause.
Has anyone else faced this type of peculiar issue while using Twilio's Verify API?
Thanks in Advance.
Robin
Just an update on how I solved this, since I feel it might be helpful for others (since no one answered it yet)
I talked to Twilio / Sendgrid support multiple times and we concluded that the slowness is due to one of the following reasons
There is a n/w delay on the system from which the API is being called. This can be debugged by loggin on to the sendgrid admin console and checking the time (and status) of each request
You might be using a free plan which limits your usage to 100 emails / day. Upgrade to essential plan that would assure a more reliable SLA. (My personal thought is that they are probably trying to move us into a paid subscription using diplomatic tactics. Anyways this again proves.. there is nothing like a free lunch)
If it is a problem with specific email addresses or providers, then it could be possible that the sender domain / address has been blacklisted or marked as spam.
In our case, we migrated to the essential plan and that solved our issue.
Thanks,
Robin
We got the request from google to submit YouTube API Audit form and we have submitted with all information but it seems our Console project with YouTube Data API still not activated properly because of status display "Active" but the daily quota is blank.
When I am going to update daily quota with any number but it seems set with blank on page refresh and we are not able to make any single request successful.
We are working with this console project and YouTube API for the last 5 years without any issue but in the last few months we are getting so many issues like first, we have verified OAuth screen with requested scopes and it has taken 20-25 days in the verification process and published. Now, facing another issue about limit quota and audit form.
Right now we are getting below error as attached in screenshot while going to authenticate my google account with the permission of Manage YouTube data API.
There is no contact support provided and I have submitted form 3 times but no back reply from support so waiting since 1 month to get work as normal.
Let me know if anyone has idea!
Error:
Error calling GET https://www.googleapis.com/youtube/v3/channels?part=contentDetails&mine=true:
(403) Access Not Configured. YouTube Data API has not been used in project xxxxxxx before or it is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=xxxxxxx then retry.
If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.
Access Not Configured. Quota limit issue
This means that you do not have any quota to use the API. You need to apply for an additional quota within the Google developer console. It took me about three months to get a quota on my project.
This is not the same as going through the verification process all though it is similar. Unfortunately, you must have missed an email you were probably notified a while ago that Google was locking down the quotas and you should apply before losing the quota on your existing project.
There is no support other than going though the form and simply waiting until google choices to grant you some quota or they tell you they wont. This is the price of developing with a free api google gets chose how they want to allow us to access things.
I use API Asana in "MyAsana" to follow my Workspace (Project) in Asana.
The API is used in 10 smartphones from different people to follow the task of projects.
After 2 days, the API does not respond. All applications authorized in Asana do not respond.
I reset the API & it works in MyAsana. and today the same problem.
I have to do a reset and change the API in all phones.
Error is: UNEXEPTED ERROR WHILE CONNECTING WITH ASANA.THIS IS MOST LIKELY A PROBLEM WITH ASANA SERVER. Please try again later.
How can I fix this please?
Asana is currently having some problems with its service and has had to temporarily shut down access to the API while it addresses them. Follow #asana on twitter and you should get a tweet when access is restored.
After running smoothly for an entire year, a 'create' call to the Google Documents List API started giving 403 Forbidden errors.
Other methods work fine with the same access_token parameter. This started around December 7th very consistently across all of our users invoking this call.
This API just recently got a deprecation policy where it will stay intact until April 2015. To be fair, I don't expect the Google Drive team to be actively supporting this API, but wondering if there is a chance that something on the Google Drive transition could be related to this inconsistency.
Is anyone else experiencing unexpected errors on the Google Documents List API? Any clues as to what is going on, and how deep might the issue be?
Thank you!
as of about 3 hours ago every call to the Doclist API using 2-legged OAuth started failing with "500 Internal Error" messages.
We have verified this from multiple systems (App Engine and local apps) using different libraries, and across domains in Asia, US and Europe.
The problem does NOT occur if normal user authentication is used - only 2LO is affected.
Unfortunately this issue affects thousands of students using our tools.
http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3233&thanks=3233&ts=1347419864
Jan
This is tracked at http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3233 and the fix should be live very soon.
UPDATE: everything is now back to normal