One of my users can't connect to his Google Analytics account from my
Cocoa app. He always gets the error "User Rate Limit Exceeded".
From what he tells me I think the authentication goes through, but
when my app tries to fetch the number of website profiles the error is
returned.
I have increased the Per-User Limit from 1 to 20 requests per second,
but that didn't help. Also, he is the only one with that error. All
other users have been fine even with requests limited to 1 per second.
Daily requests are far below daily quota.
Is there any other reason why the above error could be returned?
Thanks for the link. I posted a question to the management API group, but no response yet.
In the meantime I refactored my code to use batched requests. However, a few queries in the batch still fail with "*User Rate Limit Exceeded".*
I must be missing something, because the setup seems straight forward:
(1) Run normal (unbatched) query for the management account list
*Sleep 5 seconds (for testing)*
(2) Run a second query, batched, for all web properties (in my case just one sub-query)
*Sleep another 5 seconds (for testing)*
(3) Run a third query, batched, for all website profiles (20 sub-queries in my case)
-> A few sub-queries in the batch fail each time
I don't understand why the rate limit would be exceeded. The way I understand the above is that I'm executing* a total of only 3 queries, each with a 5 second break in-between*. Rate limit in the API console is 20 requests per second (I also tried 2000 per second).
A mis-configured client (in the Google API console) or requests without the
ID required by the API (the API key, or the OAuth 2 client ID) can also
cause quota failures.
Be sure to check the requests in the http logs generated by the library to
verify that an appropriate request header is included.
On Wednesday, May 9, 2012 5:25:02 PM UTC+2, Greg Robbins wrote:
> A mis-configured client (in the Google API console) or requests without > the ID required by the API (the API key, or the OAuth 2 client ID) can also > cause quota failures.
> Be sure to check the requests in the http logs generated by the library to > verify that an appropriate request header is included.