kotmyrevich / analytics-issues

Automatically exported from code.google.com/p/analytics-issues
0 stars 0 forks source link

Inconsistent Errors #767

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

---------------------------------------------------------------------------
Name of affected component: Core Reporting API

Name of related library and version, if applicable: Javascript and Google App 
Script

Issue summary:
My app pulls blog post data through the Core Reporting API. Every time I run 
the app I get an "Internal Error" for certain posts, and then when I run it 
again, the API will work fine and other posts that worked last time will return 
an "Internal Error". 

Steps to reproduce issue:
I can't reproduce the issue at the same point each time. It's hit and miss 
whether it works. 

Expected output:
Google Analytics to return requested metrics. 

Actual results:
Error message that reads: There was an internal error.

Notes:

Original issue reported on code.google.com by ke...@pr2020.com on 28 Oct 2015 at 1:53

GoogleCodeExporter commented 8 years ago
We have the same problem (with the PHP client [v1.1.5]).

We're also seeing "(503) There was a temporary error. Please try again later."

Original comment by glen...@gmail.com on 3 Nov 2015 at 9:53

GoogleCodeExporter commented 8 years ago
This was a temporary issue and was fixed.

Original comment by mcoh...@google.com on 6 Nov 2015 at 7:21

GoogleCodeExporter commented 8 years ago
I'm still seeing "(503) There was a temporary error". What does this mean?

Original comment by glen...@gmail.com on 6 Nov 2015 at 9:50

GoogleCodeExporter commented 8 years ago
If that is the case then I think your issue is probably unrelated to the issue 
we saw on 10/28.

A 500 or 503 error might result during heavy load or for larger more complex 
requests. For larger requests consider requesting data for a shorter time 
period. Also consider implementing exponential backoff. The frequency of these 
errors can be dependent on the view (profile) and the amount of reporting data 
associated with that view; A query that causes a 500 or 503 error for one view 
(profile) will not necessarily cause an error for the same query with a 
different view (profile).

https://developers.google.com/analytics/devguides/reporting/core/v3/coreErrors#b
ackoff

Original comment by mcoh...@google.com on 6 Nov 2015 at 10:22

GoogleCodeExporter commented 8 years ago
I think the issue is that we're requesting data for a period of time that is 
too large, meaning that the query takes too long to execute, and subsequently 
times out.

I've posted a question on StackOverflow(*) to ask whether there are any APIs 
that allow us to request aggregate data instead of scanning all page view 
records.

* 
http://stackoverflow.com/questions/33607178/getting-page-views-and-other-data-fo
r-a-single-url-or-similar-urls

Original comment by glen...@gmail.com on 9 Nov 2015 at 10:49