RE: [6-2608000025997] Random RateExceededError with rateName=RATE_LIMIT using v201806

[googleadsapi-forumadvisor via AdWords API and Google Ads API Forum]

Hi Andreas,

This issue should be fixed. Can you please verify if you still experience
the same issue?


Thanks,
Poki, Google Ads API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/13/19 02:57:22 aperico@gmail.com wrote:

Hello,
thank you for getting back to me!
I ran "Get keyword traffic estimates
"
SDK example 30 times about 10 seconds apart and got no rate exceeded. Then
I tried the GetKeywordIdeas SDK example and got rate exceeded RATE_LIMIT on
the second try.

I also started running new ads on the 726-xxx-xxx account (which is the
account I use for API queries now) three days ago to see if that would
indeed help. It has displayed about 20k ads by now (I do not want to spend
much money on ads before I get this sorted). It seems it did not help, are
there certain limits to spendings or number of ads displayed etc that need
to be met to unlock the API rate limit? If this is indeed the case that you
need active ads running?

On Tuesday, March 12, 2019 at 8:59:46 PM UTC+1, googleadsapi-forumadvisor
wrote:

Hi Andreas,

Would you mind running these examples and see if you get rate limited
errors?

- Get keyword traffic estimates

- Get campaigns


I'm trying to see if this is service specific issue.


Thanks,
Poki, AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/07/19 01:38:33 aperi...@gmail.com wrote:

Thank you for your reply,
I had read that section a couple of times when searching for the problem. I
do not interpret the text the way that you need active ads? It only says
that new accounts can have this problem?

When you implement queuing or rate limiter strategies, it's important to
keep in mind that a new Google Ads account may have a significantly more
restrictive rate limit (i.e., lower QPS) than established accounts.



Typically, the more restrictive limits on new Google Ads accounts are
relaxed once the account has published ads.


Maybe I do not understand the definition of established account, two of the
accounts I am testing on are started years ago and have spent 10s of
thousands EUR on ads. Are they not considered established?  Would having an
active ad campaign solve this even though it is never mentioned in that
section? I don't want to be confronting, I just want to be sure if this is
indeed a fix.

Thank you!



On Thursday, March 7, 2019 at 1:51:49 AM UTC+1, googleadsapi-forumadvisor
wrote:

Hi Andreas,

I looked into your account from your SOAP XML and noticed the account does
not have any active ads. Please read this section
  
which

is relevant to your issue. My recommendation would be choosing an account
that has an active campaign with recent ad spend, or create a test account

to test the code sample.


Thanks,
Poki, AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/05/19 01:38:25 aperi...@gmail.com wrote:

*edit*

I just saw that I am already using batching, in fact, your SDK example is
by default. I have not got further than to use your own SDK example:  
GetKeywordIdeas.java,

since I can not reliably use it without getting random rate exceeded errors.

// Create related to query search parameter.
RelatedToQuerySearchParameter relatedToQuerySearchParameter =
new RelatedToQuerySearchParameter();

relatedToQuerySearchParameter.setQueries(keywords.toArray(new String[0]));
searchParameters.add(relatedToQuerySearchParameter);




On Tuesday, March 5, 2019 at 7:10:25 AM UTC+1, Andreas Toresäter wrote:

Hello and thank you for the answer.
From the details I can read on all this there must then be a specific
problem with my dev token and a copy paste standard answer will not do?

Based on the details shared, it looks like you're receiving an error with
the rate scope as Account. This indicates that application is making a high
number 

RE: [6-2608000025997] Random RateExceededError with rateName=RATE_LIMIT using v201806

[googleadsapi-forumadvisor via AdWords API and Google Ads API Forum]

Hi Andreas,

Based on what you shared, it seems like you are only rate limited to
TargetingIdeaService, which is not related to active ads. I'll look further
into it. Sorry for the confusion.


Thanks,
Poki, AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/13/19 02:57:22 aperico@gmail.com wrote:

Hello,
thank you for getting back to me!
I ran "Get keyword traffic estimates
"
SDK example 30 times about 10 seconds apart and got no rate exceeded. Then
I tried the GetKeywordIdeas SDK example and got rate exceeded RATE_LIMIT on
the second try.

I also started running new ads on the 726-xxx-xxx account (which is the
account I use for API queries now) three days ago to see if that would
indeed help. It has displayed about 20k ads by now (I do not want to spend
much money on ads before I get this sorted). It seems it did not help, are
there certain limits to spendings or number of ads displayed etc that need
to be met to unlock the API rate limit? If this is indeed the case that you
need active ads running?

On Tuesday, March 12, 2019 at 8:59:46 PM UTC+1, googleadsapi-forumadvisor
wrote:

Hi Andreas,

Would you mind running these examples and see if you get rate limited
errors?

- Get keyword traffic estimates

- Get campaigns


I'm trying to see if this is service specific issue.


Thanks,
Poki, AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/07/19 01:38:33 aperi...@gmail.com wrote:

Thank you for your reply,
I had read that section a couple of times when searching for the problem. I
do not interpret the text the way that you need active ads? It only says
that new accounts can have this problem?

When you implement queuing or rate limiter strategies, it's important to
keep in mind that a new Google Ads account may have a significantly more
restrictive rate limit (i.e., lower QPS) than established accounts.



Typically, the more restrictive limits on new Google Ads accounts are
relaxed once the account has published ads.


Maybe I do not understand the definition of established account, two of the
accounts I am testing on are started years ago and have spent 10s of
thousands EUR on ads. Are they not considered established?  Would having an
active ad campaign solve this even though it is never mentioned in that
section? I don't want to be confronting, I just want to be sure if this is
indeed a fix.

Thank you!



On Thursday, March 7, 2019 at 1:51:49 AM UTC+1, googleadsapi-forumadvisor
wrote:

Hi Andreas,

I looked into your account from your SOAP XML and noticed the account does
not have any active ads. Please read this section
  
which

is relevant to your issue. My recommendation would be choosing an account
that has an active campaign with recent ad spend, or create a test account

to test the code sample.


Thanks,
Poki, AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/05/19 01:38:25 aperi...@gmail.com wrote:

*edit*

I just saw that I am already using batching, in fact, your SDK example is
by default. I have not got further than to use your own SDK example:  
GetKeywordIdeas.java,

since I can not reliably use it without getting random rate exceeded errors.

// Create related to query search parameter.
RelatedToQuerySearchParameter relatedToQuerySearchParameter =
new RelatedToQuerySearchParameter();

relatedToQuerySearchParameter.setQueries(keywords.toArray(new String[0]));
searchParameters.add(relatedToQuerySearchParameter);




On Tuesday, March 5, 2019 at 7:10:25 AM UTC+1, Andreas Toresäter wrote:

Hello and thank you for the answer.
From the details I can read on all this there must then be a specific
problem with my dev token and a copy paste standard answer will not do?

Based on the details shared, it looks like you're receiving an error 

Re: [6-2608000025997] Random RateExceededError with rateName=RATE_LIMIT using v201806

[Andreas Toresäter]

Hello,
thank you for getting back to me!
I ran "Get keyword traffic estimates 
"
 
SDK example 30 times about 10 seconds apart and got no rate exceeded. Then 
I tried the GetKeywordIdeas SDK example and got rate exceeded RATE_LIMIT on 
the second try.

I also started running new ads on the 726-xxx-xxx account (which is the 
account I use for API queries now) three days ago to see if that would 
indeed help. It has displayed about 20k ads by now (I do not want to spend 
much money on ads before I get this sorted). It seems it did not help, are 
there certain limits to spendings or number of ads displayed etc that need 
to be met to unlock the API rate limit? If this is indeed the case that you 
need active ads running?

On Tuesday, March 12, 2019 at 8:59:46 PM UTC+1, googleadsapi-forumadvisor 
wrote:
>
> Hi Andreas,
>
> Would you mind running these examples and see if you get rate limited 
> errors?
>
> - Get keyword traffic estimates 
> 
> - Get campaigns 
> 
>
> I'm trying to see if this is service specific issue. 
>
>
> Thanks,
> Poki, AdWords API Team
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and discussion group:
> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
> https://developers.google.com/adwords/api/community/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> On 03/07/19 01:38:33 aperi...@gmail.com  wrote:
>
> Thank you for your reply,
> I had read that section a couple of times when searching for the problem. 
> I do not interpret the text the way that you need active ads? It only says 
> that new accounts can have this problem?
>
> When you implement queuing or rate limiter strategies, it's important to 
> keep in mind that a new Google Ads account may have a significantly more 
> restrictive rate limit (i.e., lower QPS) than established accounts.
>
>  
>
> Typically, the more restrictive limits on new Google Ads accounts are 
> relaxed once the account has published ads. 
>
>
> Maybe I do not understand the definition of established account, two of 
> the accounts I am testing on are started years ago and have spent 10s of 
> thousands EUR on ads. Are they not considered established?  Would having an 
> active ad campaign solve this even though it is never mentioned in that 
> section? I don't want to be confronting, I just want to be sure if this is 
> indeed a fix.
>
> Thank you!
>
>
>
> On Thursday, March 7, 2019 at 1:51:49 AM UTC+1, googleadsapi-forumadvisor 
> wrote:
>
> Hi Andreas,
>
> I looked into your account from your SOAP XML and noticed the account does 
> not have any active ads. Please read this section 
> 
>  which 
> is relevant to your issue. My recommendation would be choosing an account 
> that has an active campaign with recent ad spend, or create a test account 
> 
>  
> to test the code sample. 
>
>
> Thanks,
> Poki, AdWords API Team
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and discussion group:
> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
> https://developers.google.com/adwords/api/community/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> On 03/05/19 01:38:25 aperi...@gmail.com wrote:
>
> *edit*
>
> I just saw that I am already using batching, in fact, your SDK example is 
> by default. I have not got further than to use your own SDK example: 
> GetKeywordIdeas.java, 
> since I can not reliably use it without getting random rate exceeded errors.
>
> // Create related to query search parameter.
> RelatedToQuerySearchParameter relatedToQuerySearchParameter =
> new RelatedToQuerySearchParameter();
>
> relatedToQuerySearchParameter.setQueries(keywords.toArray(new String[0]));
> searchParameters.add(relatedToQuerySearchParameter);
>
>
>
>
> On Tuesday, March 5, 2019 at 7:10:25 AM UTC+1, Andreas Toresäter wrote:
>
> Hello and thank you for the answer.
> From the details I can read on all this there must then be a specific 
> problem with my dev token and a copy paste standard answer will not do?
>
> Based on the details shared, it looks like you're receiving an error with 
> the rate scope as Account. This indicates that application is making a high 
> number of requests per second on a single AdWords account.
>
>
> The details I shared was that there are minutes apart of the requests.
>
> You could wait at least the amount of time specified in the 
> retryAfterSeconds and retry the request again.
>
>
> 

RE: [6-2608000025997] Random RateExceededError with rateName=RATE_LIMIT using v201806

[googleadsapi-forumadvisor via AdWords API and Google Ads API Forum]

Hi Andreas,

Would you mind running these examples and see if you get rate limited
errors?

- Get keyword traffic estimates

- Get campaigns


I'm trying to see if this is service specific issue.


Thanks,
Poki, AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/07/19 01:38:33 aperico@gmail.com wrote:

Thank you for your reply,
I had read that section a couple of times when searching for the problem. I
do not interpret the text the way that you need active ads? It only says
that new accounts can have this problem?

When you implement queuing or rate limiter strategies, it's important to
keep in mind that a new Google Ads account may have a significantly more
restrictive rate limit (i.e., lower QPS) than established accounts.



Typically, the more restrictive limits on new Google Ads accounts are
relaxed once the account has published ads.


Maybe I do not understand the definition of established account, two of the
accounts I am testing on are started years ago and have spent 10s of
thousands EUR on ads. Are they not considered established?  Would having an
active ad campaign solve this even though it is never mentioned in that
section? I don't want to be confronting, I just want to be sure if this is
indeed a fix.

Thank you!



On Thursday, March 7, 2019 at 1:51:49 AM UTC+1, googleadsapi-forumadvisor
wrote:

Hi Andreas,

I looked into your account from your SOAP XML and noticed the account does
not have any active ads. Please read this section
  
which

is relevant to your issue. My recommendation would be choosing an account
that has an active campaign with recent ad spend, or create a test account

to test the code sample.


Thanks,
Poki, AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/05/19 01:38:25 aperi...@gmail.com wrote:

*edit*

I just saw that I am already using batching, in fact, your SDK example is
by default. I have not got further than to use your own SDK example:  
GetKeywordIdeas.java,

since I can not reliably use it without getting random rate exceeded errors.

// Create related to query search parameter.
RelatedToQuerySearchParameter relatedToQuerySearchParameter =
new RelatedToQuerySearchParameter();

relatedToQuerySearchParameter.setQueries(keywords.toArray(new String[0]));
searchParameters.add(relatedToQuerySearchParameter);




On Tuesday, March 5, 2019 at 7:10:25 AM UTC+1, Andreas Toresäter wrote:

Hello and thank you for the answer.
From the details I can read on all this there must then be a specific
problem with my dev token and a copy paste standard answer will not do?

Based on the details shared, it looks like you're receiving an error with
the rate scope as Account. This indicates that application is making a high
number of requests per second on a single AdWords account.


The details I shared was that there are minutes apart of the requests.

You could wait at least the amount of time specified in the
retryAfterSeconds and retry the request again.


Yes, as I said in my question I do that.

 You will need to consider all requests made against that account
irrespective of whether the call was made via API or web interface.


I am the only one making calls for these 3 accounts, and I do it by
manually doing one query with one operation at the time from my IDE.

Please note that the API call might still fail as the rate limits are not
based on a constant QPS and are subjected to change.


What exactly does this mean? Do you say I can get this error even if I do
let's say 1 request with one operation every hour?

For the Rate limits, when you retry the requests, your application should
use an exponential backoff policy

.


How will this help if I still get this error when I just tried a query
after waiting for the whole night?

Please take a look at the system limits guide
  
for

the TargetingIdea specific limits.


I am not getting any of those errors and I am well below the limits for

RE: [6-2608000025997] Random RateExceededError with rateName=RATE_LIMIT using v201806

[googleadsapi-forumadvisor via AdWords API and Google Ads API Forum]

Hi Andreas,

I'm looking into the exact issue and explanation. I will keep you posted
once I have an update. Thank you very much for your patience.



Thanks,
Poki, AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/07/19 01:38:33 aperico@gmail.com wrote:

Thank you for your reply,
I had read that section a couple of times when searching for the problem. I
do not interpret the text the way that you need active ads? It only says
that new accounts can have this problem?

When you implement queuing or rate limiter strategies, it's important to
keep in mind that a new Google Ads account may have a significantly more
restrictive rate limit (i.e., lower QPS) than established accounts.



Typically, the more restrictive limits on new Google Ads accounts are
relaxed once the account has published ads.


Maybe I do not understand the definition of established account, two of the
accounts I am testing on are started years ago and have spent 10s of
thousands EUR on ads. Are they not considered established?  Would having an
active ad campaign solve this even though it is never mentioned in that
section? I don't want to be confronting, I just want to be sure if this is
indeed a fix.

Thank you!



On Thursday, March 7, 2019 at 1:51:49 AM UTC+1, googleadsapi-forumadvisor
wrote:

Hi Andreas,

I looked into your account from your SOAP XML and noticed the account does
not have any active ads. Please read this section
  
which

is relevant to your issue. My recommendation would be choosing an account
that has an active campaign with recent ad spend, or create a test account

to test the code sample.


Thanks,
Poki, AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/05/19 01:38:25 aperi...@gmail.com wrote:

*edit*

I just saw that I am already using batching, in fact, your SDK example is
by default. I have not got further than to use your own SDK example:  
GetKeywordIdeas.java,

since I can not reliably use it without getting random rate exceeded errors.

// Create related to query search parameter.
RelatedToQuerySearchParameter relatedToQuerySearchParameter =
new RelatedToQuerySearchParameter();

relatedToQuerySearchParameter.setQueries(keywords.toArray(new String[0]));
searchParameters.add(relatedToQuerySearchParameter);




On Tuesday, March 5, 2019 at 7:10:25 AM UTC+1, Andreas Toresäter wrote:

Hello and thank you for the answer.
From the details I can read on all this there must then be a specific
problem with my dev token and a copy paste standard answer will not do?

Based on the details shared, it looks like you're receiving an error with
the rate scope as Account. This indicates that application is making a high
number of requests per second on a single AdWords account.


The details I shared was that there are minutes apart of the requests.

You could wait at least the amount of time specified in the
retryAfterSeconds and retry the request again.


Yes, as I said in my question I do that.

 You will need to consider all requests made against that account
irrespective of whether the call was made via API or web interface.


I am the only one making calls for these 3 accounts, and I do it by
manually doing one query with one operation at the time from my IDE.

Please note that the API call might still fail as the rate limits are not
based on a constant QPS and are subjected to change.


What exactly does this mean? Do you say I can get this error even if I do
let's say 1 request with one operation every hour?

For the Rate limits, when you retry the requests, your application should
use an exponential backoff policy

.


How will this help if I still get this error when I just tried a query
after waiting for the whole night?

Please take a look at the system limits guide
  
for

the TargetingIdea specific limits.


I am not getting any of those errors and I am well below the limits for
seed keywords, at the moment I am testing with 2-3.

You can also take a look at Batching Targeting Ideas
  
to

make requests more efficiently.


I will 

Re: [6-2608000025997] Random RateExceededError with rateName=RATE_LIMIT using v201806

[Andreas Toresäter]

Thank you for your reply,
I had read that section a couple of times when searching for the problem. I 
do not interpret the text the way that you need active ads? It only says 
that new accounts can have this problem?

When you implement queuing or rate limiter strategies, it's important to 
> keep in mind that a new Google Ads account may have a significantly more 
> restrictive rate limit (i.e., lower QPS) than established accounts.

 

> Typically, the more restrictive limits on new Google Ads accounts are 
> relaxed once the account has published ads. 


Maybe I do not understand the definition of established account, two of the 
accounts I am testing on are started years ago and have spent 10s of 
thousands EUR on ads. Are they not considered established?  Would having an 
active ad campaign solve this even though it is never mentioned in that 
section? I don't want to be confronting, I just want to be sure if this is 
indeed a fix.

Thank you!



On Thursday, March 7, 2019 at 1:51:49 AM UTC+1, googleadsapi-forumadvisor 
wrote:
>
> Hi Andreas,
>
> I looked into your account from your SOAP XML and noticed the account does 
> not have any active ads. Please read this section 
> 
>  which 
> is relevant to your issue. My recommendation would be choosing an account 
> that has an active campaign with recent ad spend, or create a test account 
> 
>  
> to test the code sample. 
>
>
> Thanks,
> Poki, AdWords API Team
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and discussion group:
> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
> https://developers.google.com/adwords/api/community/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> On 03/05/19 01:38:25 aperi...@gmail.com  wrote:
>
> *edit*
>
> I just saw that I am already using batching, in fact, your SDK example is 
> by default. I have not got further than to use your own SDK example: 
> GetKeywordIdeas.java, 
> since I can not reliably use it without getting random rate exceeded errors.
>
> // Create related to query search parameter.
> RelatedToQuerySearchParameter relatedToQuerySearchParameter =
> new RelatedToQuerySearchParameter();
>
> relatedToQuerySearchParameter.setQueries(keywords.toArray(new String[0]));
> searchParameters.add(relatedToQuerySearchParameter);
>
>
>
>
> On Tuesday, March 5, 2019 at 7:10:25 AM UTC+1, Andreas Toresäter wrote:
>
> Hello and thank you for the answer.
> From the details I can read on all this there must then be a specific 
> problem with my dev token and a copy paste standard answer will not do?
>
> Based on the details shared, it looks like you're receiving an error with 
> the rate scope as Account. This indicates that application is making a high 
> number of requests per second on a single AdWords account.
>
>
> The details I shared was that there are minutes apart of the requests.
>
> You could wait at least the amount of time specified in the 
> retryAfterSeconds and retry the request again.
>
>
> Yes, as I said in my question I do that.
>
>  You will need to consider all requests made against that account 
> irrespective of whether the call was made via API or web interface.
>
>
> I am the only one making calls for these 3 accounts, and I do it by 
> manually doing one query with one operation at the time from my IDE.
>
> Please note that the API call might still fail as the rate limits are not 
> based on a constant QPS and are subjected to change.
>
>
> What exactly does this mean? Do you say I can get this error even if I do 
> let's say 1 request with one operation every hour?
>
> For the Rate limits, when you retry the requests, your application should 
> use an exponential backoff policy 
> 
> .
>
>
> How will this help if I still get this error when I just tried a query 
> after waiting for the whole night? 
>
> Please take a look at the system limits guide 
> 
>  for 
> the TargetingIdea specific limits.
>
>
> I am not getting any of those errors and I am well below the limits for 
> seed keywords, at the moment I am testing with 2-3. 
>
> You can also take a look at Batching Targeting Ideas 
> 
>  to 
> make requests more efficiently.
>
>
> I will look into this but I do not see how it will help in my case since I 
> get the error when I am using only a fraction of the rate limits you 
> publish.
>
> Please look into what is wrong with my dev token, thank you!
>
>
>
>
> On Monday, March 4, 2019 at 9:46:01 PM UTC+1, googleadsapi-forumadvisor 
> 

RE: [6-2608000025997] Random RateExceededError with rateName=RATE_LIMIT using v201806

[googleadsapi-forumadvisor via AdWords API and Google Ads API Forum]

Hi Andreas,

I looked into your account from your SOAP XML and noticed the account does
not have any active ads. Please read this section
  
which

is relevant to your issue. My recommendation would be choosing an account
that has an active campaign with recent ad spend, or create a test account

to test the code sample.


Thanks,
Poki, AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/05/19 01:38:25 aperico@gmail.com wrote:

*edit*

I just saw that I am already using batching, in fact, your SDK example is
by default. I have not got further than to use your own SDK example:  
GetKeywordIdeas.java,

since I can not reliably use it without getting random rate exceeded errors.

// Create related to query search parameter.
RelatedToQuerySearchParameter relatedToQuerySearchParameter =
new RelatedToQuerySearchParameter();

relatedToQuerySearchParameter.setQueries(keywords.toArray(new String[0]));
searchParameters.add(relatedToQuerySearchParameter);




On Tuesday, March 5, 2019 at 7:10:25 AM UTC+1, Andreas Toresäter wrote:

Hello and thank you for the answer.
From the details I can read on all this there must then be a specific
problem with my dev token and a copy paste standard answer will not do?

Based on the details shared, it looks like you're receiving an error with
the rate scope as Account. This indicates that application is making a high
number of requests per second on a single AdWords account.


The details I shared was that there are minutes apart of the requests.

You could wait at least the amount of time specified in the
retryAfterSeconds and retry the request again.


Yes, as I said in my question I do that.

 You will need to consider all requests made against that account
irrespective of whether the call was made via API or web interface.


I am the only one making calls for these 3 accounts, and I do it by
manually doing one query with one operation at the time from my IDE.

Please note that the API call might still fail as the rate limits are not
based on a constant QPS and are subjected to change.


What exactly does this mean? Do you say I can get this error even if I do
let's say 1 request with one operation every hour?

For the Rate limits, when you retry the requests, your application should
use an exponential backoff policy

.


How will this help if I still get this error when I just tried a query
after waiting for the whole night?

Please take a look at the system limits guide
  
for

the TargetingIdea specific limits.


I am not getting any of those errors and I am well below the limits for
seed keywords, at the moment I am testing with 2-3.

You can also take a look at Batching Targeting Ideas
  
to

make requests more efficiently.


I will look into this but I do not see how it will help in my case since I
get the error when I am using only a fraction of the rate limits you
publish.

Please look into what is wrong with my dev token, thank you!




On Monday, March 4, 2019 at 9:46:01 PM UTC+1, googleadsapi-forumadvisor
wrote:

Hello Andreas,

Based on the details shared, it looks like you're receiving an error with
the rate scope as Account. This indicates that application is making a high
number of requests per second on a single AdWords account. You could wait
at least the amount of time specified in the retryAfterSeconds and retry
the request again. You will need to consider all requests made against that
account irrespective of whether the call was made via API or web interface.
Please note that the API call might still fail as the rate limits are not
based on a constant QPS and are subjected to change.

For the Rate limits, when you retry the requests, your application should
use an exponential backoff policy
.
For example, if you first pause 5 seconds before the first retry, you could
pause 10 seconds after the second and 20 seconds after the third retry.
Exponential backoff helps ensure you are not calling the API too
aggressively. This guide
  
has

best practices that can be implemented to handle the rate limit errors.
Please take a look at the system limits guide