Error: Google can't process your query. GA's response is: 503 The service is currently unavailable.

[Hugh Gage]

I'm increasingly getting this query error code: 

Error: Google can't process your query. GA's response is: 503 The service is currently unavailable.

SM support says there is nothing they can do as it is an issue at Google's end.

Google own explanation here is as follows:

500

internalServerError

Unexpected internal server error occurred.

Do not retry this query more than once.

and 

Handling 500 or 503 responses

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).

I have started receiving this error code on queries which previously used to run fine. I've made no changes so it seems that some thing else has caused Google to return this error code. 

I noticed recently that Google Analytics API (via SM) is returning an increasing number of error codes of various descriptions. Usually they can be resolved but this one appears to be insoluble. 

Is anybody else seeing this?

[Mikael Thuneberg]

Last week, we changed our system to be in line with Google's instruction, so we no longer retry when getting that error. Previously, we retried many times, and were getting into problems with Google's quotas due to this. 

Can you identify what in particular causes these errors? We could report it to Google.

--
You received this message because you are subscribed to the Google Groups "Supermetrics" group.
To unsubscribe from this group and stop receiving emails from it, send an email to automateanalytics+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/automateanalytics.
To view this discussion on the web visit https://groups.google.com/d/msgid/automateanalytics/a23f409c-7194-4266-b001-6e0f31b243c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mikael Thuneberg]

Ok, despite what Google says, we will now retry the query once if that error appears (waiting up to 30 seconds before run. Hopefully this helps.

[Hugh Gage]

I've tried rerunning the queries with >30 seconds time gaps but to no avail. Unfortunately there is no other info given apart from what I put above. I could supply you with a query reference (it's started happening for at least 9 queries in the same report) if that would help surface any other info. Just let me know if you want these.

On Tuesday, 6 September 2016 09:17:35 UTC+1, Supermetrics Support wrote:

Ok, despite what Google says, we will now retry the query once if that error appears (waiting up to 30 seconds before run. Hopefully this helps.

On 6 September 2016 at 09:57, Mikael Thuneberg <mikael.t...@supermetrics.com> wrote:

Last week, we changed our system to be in line with Google's instruction, so we no longer retry when getting that error. Previously, we retried many times, and were getting into problems with Google's quotas due to this. 

Can you identify what in particular causes these errors? We could report it to Google.

On 6 September 2016 at 09:52, Hugh Gage <hugh...@engage-digital.com> wrote:

I'm increasingly getting this query error code: 

Error: Google can't process your query. GA's response is: 503 The service is currently unavailable.

SM support says there is nothing they can do as it is an issue at Google's end.

Google own explanation here is as follows:

500

internalServerError

Unexpected internal server error occurred.

Do not retry this query more than once.

and 

Handling 500 or 503 responses

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).

I have started receiving this error code on queries which previously used to run fine. I've made no changes so it seems that some thing else has caused Google to return this error code. 

I noticed recently that Google Analytics API (via SM) is returning an increasing number of error codes of various descriptions. Usually they can be resolved but this one appears to be insoluble. 

Is anybody else seeing this?

--
You received this message because you are subscribed to the Google Groups "Supermetrics" group.

To unsubscribe from this group and stop receiving emails from it, send an email to automateanalyt...@googlegroups.com.

[Mikael Thuneberg]

Yes please, we can check if there's anything in the logs that could explain the errors.

To unsubscribe from this group and stop receiving emails from it, send an email to automateanalytics+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/automateanalytics.

To view this discussion on the web visit https://groups.google.com/d/msgid/automateanalytics/de16188c-216a-4750-93eb-8d2759613445%40googlegroups.com.

[Hugh Gage]

I've just forwarded a spreadsheet to you with all the details. I hope it helps.

Hugh

[ad...@marketingadept.com]

Hi,

We are running into the same issue with our report (screenshot attached). Were you able to resolve the issue?

Thank you!