Re: Keep on getting Resource_Exhausted error when I should not

2024-07-10 Thread Parth Vallabhdas Makadiya
Hey, I am having similar issues on the same topic. We are using `KeywordPlanService.GenerateHistoricalMetrics`. We have standard access developer token. (So only 1QPS limit applies here.) I am getting `RESOURCE_EXHAUSTED` (yesterday everything was working fine.) I am using rate limitting and I a

Re: Keep on getting Resource_Exhausted error when I should not

2022-12-08 Thread 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
Hi, Having standard access allows for unlimited operations per day. However, you would still be subject to the rate limits or QPS limit discussed here. Encountering the RESOURCE_EXHAUSTED error when having standard access indicates that you could be performing too many requests within a short p

Re: Keep on getting Resource_Exhausted error when I should not

2022-12-08 Thread sealytic...@gmail.com
Hello, We have standard access, despite that from yesterday we are getting this error regularly. I think same with the other people, it looks there is a problem on API. Is there any limitation for Standard Access. I checked your sharing but I cannot see any there. On Wednesday, December 7, 202

Re: Keep on getting Resource_Exhausted error when I should not

2022-12-06 Thread 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
Hi everyone, Thanks for commenting in this forum thread. I understand the inconvenience you are encountering due to this issue. However, for me to request my rest of the team to look into this matter, could you provide us with the complete request and response logs with request ID generated fo

Re: Keep on getting Resource_Exhausted error when I should not

2022-12-06 Thread ro...@searchkings.ca
Just chiming in with similar feedback. We're receiving rate limit errors this morning that we've not seen at any point in the past. We have exponential retries implemented so the jobs eventually succeed, but came here to see others experiencing the same thing. We recently updated to v12 in case

Re: Keep on getting Resource_Exhausted error when I should not

2022-12-06 Thread AdWordsApiUser
We are seeing increased frequency of the same error as well. We have standard access, and have not encountered this error before. It seems to be something happening from the API. I'd request the team to check if everything is OK with the API. On Tuesday, 6 December 2022 at 19:05:19 UTC+5:30 ads

Re: Keep on getting Resource_Exhausted error when I should not

2022-12-06 Thread 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
Hi Peter and Sohail, Thank you for your reply. Kindly note that the API request and API operations are different from each other. A mutate request can have 10,000 operations per request. As said by Sohail, you are using a simple keyword idea search request. This request is the planning service

Re: Keep on getting Resource_Exhausted error when I should not

2022-12-06 Thread 'Peter Lanser' via Google Ads API and AdWords API Forum
message. > > > > Is there something else I should look? > > > > > > Thanks > > Sohail > > > > > > *From: *Google Ads API Forum Advisor > *Sent: *Monday, December 5, 2022 7:54 AM > *To: *sohai...@gmail.com > *Cc: *adwor...@go

RE: Keep on getting Resource_Exhausted error when I should not

2022-12-05 Thread Sohail Zahid
Resource_Exhausted error when I should not Hi Sohail,Thanks for reaching out to the Google Ads API team. I hope you are doing well today. Kindly note that the RESOURCE_EXHAUSTED error generally occurs when you are sending too many requests in a short period of time. The server throws this error once it

RE: Keep on getting Resource_Exhausted error when I should not

2022-12-05 Thread 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
Hi Sohail, Thanks for reaching out to the Google Ads API team. I hope you are doing well today. Kindly note that the RESOURCE_EXHAUSTED error generally occurs when you are sending too many requests in a short period of time. The server throws this error once it detects that your request has e