What time is does the daily Google Photos API Quota Reset? - google-photos

I currently have a usage quota of 4,000,000 requests per day via the Google Photo Library API. We're doing a large promotion of our product which has now blown through the quota.
I'm now receiving an error code 429. Does anyone know what time of day the quota resets?

Reading the docs, it will reset in the next day, after midnight.
You can also request additional quota limit

Related

Quota exceeded error when create new profile with GC Talent Solution

Step to reproduce: Go to this site, https://cloud.google.com/talent-solution/job-search/docs/reference/rest/v4beta1/projects.tenants.profiles/create, make a POST request with a valid tenant name, to create a new profile.
Get error: "8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'quota metric that handles profile write requests' and limit 'quota metric that handles profile write requests per minute' of service 'jobs.googleapis.com' for consumer 'project_number:XXXXXXXXX'."
My current usage is just 100+ post/put/delete requests per month, and if I remember correctly, free tie in Google Cloud allows thousands of requests per 100 seconds.
My billing account was setup and the card is valid. I can create companies, tenants as normal.
Please help.
As John Hanley commented quota issues are usually handled by the Cloud Support team and should be addressed opening a support ticket. However, this case refers to Cloud Talent Solution Profile Search which as stated in the documentation at this moment is in 'Closed Beta' state, meaning that it doesn't allow new candidates.
In order to use this feature you will have to wait until it's released to the public or the Beta is opened for new candidates.

How does the quota limit for Google Civic Information API work?

I ask because the errors don't seem to line up with what the documentation says.
We have a daily limit of 1 million requests. Upon reaching about 995,000 requests, we started getting errors about hitting the limit and requests flat-lined. This happened around 7:20pm. The dashboard says "Daily quotas reset at midnight Pacific Time (PT)". However, requests started going through again at about 8:30pm.
Since 995,000 < 1,000,000 and 8:30pm != midnight, this leaves me with the feeling that we can't actually predict and prevent hitting the rate limit, or know when it will reset.
What do I need to know in order to do occasional heavy-use of the API while staying under the limits? Nothing in the documentation or dashboards gives me what I need.
You can see all your API quotas on the Google Cloud Console's "IAM & admin" page's "Quotas" tab. It should contain the details on how much you have used and whether or not you hit the limit. If you only used 995,000 / 1,000,000 and it show as such in your quota page (give it a bit of time to update since it might have delay) and it doesn't work, there's something wrong and should be reported to us directly.
I suspect you might be hitting a rate limit, which temporary prevented you from making further requests. You just have to bring your rate below the limit to have it working again. The quota page contain information on the rate limit (per 100 seconds) as well.
Your official support channels for Civic Information API is here.

Audit Report API Limit Increase

I need to access Google Docs Audit Activity for my domain. The limit for the same is 1000 records in a single API call. Also, the number of API calls per day is 10K.
What is the way to increase the limits for API calls per day? Google Support is unable to answer this question and redirected me to Stack Overflow.
You may want to refer with this thread regarding quota increase for Report API:
There are several quotas for the Google Analytics APIs and Google APIs in general.
requests/day 0 of 50,000
requests/100seconds/user 100
requests/perView 10000
Your application can make 50000 requests per day by default. This can be extended but it takes a while to get permission when you are getting close to this limit around 80% its best to request an extension at that time.
Your user can max make 100 requests a second which must be something that has just gone up last I knew it was only 10 requests a second. User is denoted by IP address. There is no way to extend this quota more then the max you cant apply for it or pay for it.
Then there is the last quota the one you asked about. You can make max 10000 requests a day to a view. This isn't just application based if the user runs my application and your application then together we have only 10000 requests that can be made. This quota is a pain if you ask me. Now for the bad news there is no way to extend this quota you cant apply for it you cant pay for it and you cant beg the Google Analytics dev team (I have tried)
Answer: No you cant extend the per view per day quota limit.
If you encountered error, it is recommended to catch the exception and, using an exponential backoff algorithm, wait for a small delay before retrying the failed call.

GCS / GCML services blocked with incorrect error (management CRUD quota exceeded)

Yesterday my free subscription validity got over, and I registered for the GCML services. However, I am not able to access my GCS or GCML resources and am getting Access Denied errors. On trying to access the Jobs page on the console I get the following error
Quota failure for project_number:836740678279 -- The allowed Cloud ML quota for API calls in the "Management (CRUD) requests" group is exceeded, please see https://console.cloud.google.com/apis/api/ml.googleapis.com/quotas for details.
However the limit on quota is 10,000 per day, and I had only used up 105 on the said day (viewed on the graphs as pointed in the error message)
You're right in that the default daily quota for CRUD requests (Create/Read/Update/Delete) is 10,000, however there is also a 100-second quota, which is set to 50 by default. Most likely you sent too many requests within 100 seconds and exceeded it.
Note that you can increase the 100-second quota limit to 500 for your project at the
quota management page, which was linked from the error message.
I was getting the same error. Turns out I needed to setup a billing account (https://console.cloud.google.com/billing) for the project.

Google Cloud Pub/Sub on Google App Engine hits QPS limit too soon

Around 90 or 100 calls per second to
pubsub_client.projects().topics().publish(topic='projects/xxxx',body=body).execute(num_retries=0)
per second from Google App Engine App to Google Cloud Pub/Sub, results in
HttpError: <HttpError 429 when requesting https://pubsub.googleapis.com/v1/projects/xxxx:publish?alt=json returned "Request throttled due to user QPS limit being reached.">
I know there is a limit on administrative operations at 100 QPS, but certainly publishing to a topic is not an administrative operation? I know pub/sub should support millions of operations per second so I know there's something wrong.
Any help or insight would be appreciated. I need to get up to at least 300 publishes per second, trying to streamline an existing implementation using pubsub. I think this may be a bug with the implementation.
I am running this code on Google App Engine python 2.7 -- using the appengine runtime, not the flexible one as that's not approved for production code yet.
Note that publisher quota is not in terms of QPS, but in terms of throughput. The default limit is 100MB/s. See the Quotas documentation for more details. Depending on the message size you are sending, you may be running into these limits.
The "user QPS limit being reached" message on a publish usually means one of three things:
You are publishing at a throughput that is higher than the default 100MB/s quota. If that is the case, then you can apply for more quota by clicking on the "Apply for higher quota" on the Pub/Sub Quota page.
You are not authenticated against the correct Cloud project. If you are authenticated in or running your Google App Engine instances in a Cloud project that differs from the one your topic is defined in, the quota you run into may not be defined in the project you expect. More information can be found in the Google Application Defaults Credentials page.
You have manually set quota in the Quota page and that is the limit you are running into.