I had some issues in the production environment with error "403: User Rate Limit Exceeded" when using the google calendar api. The error description page suggested to change the user limit in the developer console.
Logging into the developer console i did see a user limit of '5 requests/second/user' as seen in
After clicking on the pencil, i saw
Because i was unable to put in any number, i ended up deleting the content of the box and saving it. After that the api was unavailable due to 'not enabled'.
To try and restore the previous state of the api, i disabled it in the developer console and re-enabled it. This does not have the indended behaviour:
So now i'm stuck with an api with no global quota and a zero user limit, which can not be changed (no pencil to be seen anywhere).
I need to get this service restored asap.
Note: this behaviour is reproduceable on any new project by adding the google calendar api and following my steps.
I filed a quota increase request with explanation in the comment to google.
They responded today:
Hello xxxxx,
Thanks for reporting the configuration error you're seeing for your app (Project ID xxxxx) when setting your "per-user" limit to 0.
I've increased your "per-user" limit back to 5, you should see this amount in your console now.
Apologies for any inconvenience you may have experienced.
Regards,
Frank
Developer Platform
In the developer console i can see the quotas and the limit of 5 requests/sec/user. The service is also back up.
Thanks Frank from the Google Developer Platform.
Related
This is strange we have started receiving too many per day (nearly 300-500 times)
googleapi: Error 500: Internal error encountered., backendError
while calling Admin SDK Directory API. https://developers.google.com/admin-sdk/directory
Google chat support for API is removed and Facing issue with how to address the problem. Our rate limit and query calls are way in the limits. We query Admin SDK as a cronjob schedule.
Is there a way we can debug 500 errors for AdminSDK
Is there any information regarding which deployment Region of Google is more capable to handle load?
No error on console
Logs error
Contact Workspace Support or File a Bug
As DalmTo pointed out, 500 errors are usually out of your control. Especially in this case since you are calling Google's servers.
The best option to debug these errors is probably contacting support directly. You can find the corresponding contact information for your Workspace account on this page.
https://support.google.com/a/answer/1047213?hl=en
If you are able to regularly reproduce this and you think its a bug, fill out the template here:
https://issuetracker.google.com/issues/new?component=191635&template=824102
Ensure to include your code, complete reproduction steps, some evidence/statistics of the failures, and any other information you can give.
This usually happens when the Google Cloud Platform service account used for authentication was created after the in-app products.
To solve this, make a trivial edit to your in-app products in the Google Play Console. For example, add a temporary tag. Then try again to make the request and it should succeed.
By the way, the same is true for the purchases.voidedpurchases which reports an "insufficient permissions" error.
Today I try to enable Google+ API on API Manager and it said
Error: failed to do requirement checks
What wrong? I just disable it and I want to re-enable again.
This is most likely an outage on Google Developer console even though I am not seeing it on the status page.
There for the fastest way to get it resolved will be to go to the upper right hand corner in google developer console look for the !. Send feed back.
You cant feed back the actually error as its a popup but you can feed back from the screen before you attempt to enable an error.
I am having the same problem. Perhaps it is an outage.
Evidence: I count 5 people here so far that have the issue, and no google results for that exact error message. "Error: failed to do requirement checks" That means, it's a new error, and google's crawler hasn't had time to scrape even this question yet.
It's okay now, I just re-enabling the API and it works.
I think its outage
I've created a Google Hangout extension app, tested it works privately etc and now I'm trying to publish it. I have followed the instructions here:
https://developers.google.com/+/hangouts/publishing
I've filled in the forms correctly, created the O-Auth client ID, filled out the consent form etc. When I tick the Make this application public tickbox and try to save, a server error message pops up along the lines of:
Server Error
Whoops! Our bad.
Please try again. If the problem persists, please let us know using the "Send feedback" link below. Thanks!
Tracking Number: XXXXXXXXXXXXXXXXXXXXXXXXX
[Send feedback]
I've checked the Chrome console - the request gets a 500 error and in the JSON response I can see:
{"message":"Developer not registered with CWS."}
I have paid the $5 one-off developer fee on the Chrome Web Store and I am the Hangout project owner. I'm not sure what I'm missing here. I need to get this published in the next 24 hours...
Any useful insights? Is there any official support forum for Google+ platform developers?
UPDATE
I was using a Google Apps account before so I've paid the developer fee on a personal account to verify me on CWS, made this account owner of the Hangout project and I still get the same message response.
I believe then that it's basically just broken. Thanks Google.
I am using the Google Translate API (for REST). There is a quota of 2M characters/day. I would like to increase that - how do I do so?
I have followed the instructions provided to no avail.
Google Developers Console
Select Project, Expand API & Auth, Click the Translate API, Go To
Quota
I have clicked the 'Apply for higher quota' which returns a 'page
not found' error
I have clicked each 'Change' button and input a higher number.
When Submitted it sits there; there is no response.
I have also gone to the API Console, and selected Quotas under my Project. There is no link to 'Request more...' for the Translate API, as there is with other APIs.
This is a bug. It also appears in the documentation. https://cloud.google.com/translate/v2/pricing. Google has been informed they are in the process of tracking someone down to fix the issue with the file at this time.
How To increase quota from the Console
You can / or should be able to extend it from the console.
Go APIs-> click on Translation API -> look for Quota click on that
You should be able to click on Apply for Higher quota. But the link isn't working right now. Google is on it. I will update this when i hear from them that it has been fixed.
Again Well spotted, and thank you for pointing it out :)
Update: I was told by Google that you should be able to increase your quota by enabling billing. There is also a thread about this on Google's Forums
Change quota fails; Apply for higher quota URL is broken
Update 2 (direct from Google)
Fixes were pushed on February 27th, they include:
Telling the user on the Quota tab that they have to enable billing
Removing the option to change the quota when billing isn't enabled
We no longer show a red warning triangle that 0% of 0 quota has been used
What we haven't fixed is the link to the document on how to apply for a quota
increase, the bug for this has been bouncing backwards and forwards
but we seem to be closing in on a resolution.
I am trying to use the Admin SDK Directory api to look up user profiles. I am able to do this successfully all day (with in quota) with 99% of the time. Though there are certain times where it just fails no matter what.
Yes I have set the service account user, I have the proper scopes, I have admin api turned on.
It even fails in the google api explorer. See screen shots
The call:
https://www.dropbox.com/s/9v9m6s5zf76oix7/call.png?dl=0
The response:
https://www.dropbox.com/s/te6k3x5xjkr467j/response.png?dl=0
Sorry for the links, images keep showing as broken
After contacting google they supplied an answer. There is a setting for the contacts app that enables and disables this.
Admin console >> Google Apps >> Settings for Contacts >> Advanced settings
Contact sharing: Enable contact sharing
Make sure that is enabled and it works.
Here is a screen shot: https://www.dropbox.com/s/8jmzz7zw0xq4ux4/answer.png?dl=0
Honestly, it just seems like some sort of transient error on the Google side. Being that it's working ~99% of the time for you, means you're not doing anything wrong. I would consider this more true b/c you're also using a Google Tool rather than your own so you know it's not the code. When it's failing for you, does it also then fail with the API explorer? What about with the OAuth Playground?
If this is reproducible consistently (same times, after X amount of requests, etc.), it would be worth reporting the the Google for Work Support team (assuming you have the ability to contact support) as it sounds like a bug and they would be able to help with break/fix for API issues.