Hi
The latter is the case.
That was intentional change, but has been rolled back.
But in either case, it should be fixed now.
Best,
- Takeshi, AdWords API Team
On Monday, January 21, 2013 10:48:24 PM UTC+9, oseemann wrote:
>
> Was this change an unintentional mistake that is now fixed or was i
Was this change an unintentional mistake that is now fixed or was it an
intentional change that, sort of, had unforeseen consequences and has been
rolled back?
I'm asking because we have developed workarounds over the weekend
(splitting report downloads by campaign ids) and the answer might be
The last occurrence in our system was at 21st Jan 2am UTC.
That said, I found a workaround by limiting the requests to no more than a
single campaigns objects, so I wouldn't expect to see too many errors of
this type anyway.
How come it took you guys the best part of 4 days to even acknowledge
Hi,
The temporal issue was happening in our side.
The issue has been fixed now.
If you are still seeing the error, could you please post it again?
Best,
- Takeshi, AdWords API Team
On Monday, January 21, 2013 3:50:59 AM UTC+9, chris h wrote:
>
> Had same problem here. My solution was to switch
Had same problem here. My solution was to switch to OAuth 2.0 - that is
working for me. So it must be something Google changed with the
authentication.
On Sunday, January 20, 2013 12:18:26 AM UTC-5, Michael Ni wrote:
>
> same thing over here, what is going on at google?
>
> On Saturday, Januar
same thing over here, what is going on at google?
On Saturday, January 19, 2013 3:54:06 AM UTC-8, Abhinay Mehta wrote:
>
> Sorry I mean most of our reports SINCE the 17th of Jan are failing.
>
> On Saturday, January 19, 2013 11:52:48 AM UTC, Abhinay Mehta wrote:
>>
>> Could someone from Google ple
Sorry I mean most of our reports SINCE the 17th of Jan are failing.
On Saturday, January 19, 2013 11:52:48 AM UTC, Abhinay Mehta wrote:
>
> Could someone from Google please tell us what is going on? Most of our
> reports for the 17th of Jan are still failing, we need this data.
>
> On Thursday, J
Could someone from Google please tell us what is going on? Most of our
reports for the 17th of Jan are still failing, we need this data.
On Thursday, January 17, 2013 11:05:07 PM UTC, pete wrote:
>
> As of 19:00 GMT this evening, we've been getting errors when requesting
> AdHoc Reports, (Ad and
We're still getting these errors.
I've migrated to use v201209 from v201206 - other than a different error
message, still can't reliably use the AdHoc report service.
I.e.
ReportDownloadError.ERROR_GETTING_RESPONSE_FROM_BACKEND
Unable to read report data
The only success I've had is to limi
It appears as if the timeout between api frontend and backend has been
drastically reduced. Whereas before (on some cases with very large report
sizes) it used to take up to 5 minutes for the API frontend to wait and
then return the error ERROR_GETTING_RESPONSE_FROM_BACKEND, it now only
takes a
We are also seeing HTTP 500 errors this morning when trying to generate
Keyword Performance reports for some of our accounts.
On Thursday, January 17, 2013 11:05:07 PM UTC, pete wrote:
>
> As of 19:00 GMT this evening, we've been getting errors when requesting
> AdHoc Reports, (Ad and Keyword Pe
We see a similar problem. For about 10% of our managed accounts we receive
ERROR_GETTING_RESPONSE_FROM_BACKEND errors, apparently consistently.
Oliver
On Friday, January 18, 2013 12:05:07 AM UTC+1, pete wrote:
>
> As of 19:00 GMT this evening, we've been getting errors when requesting
> AdHoc R
12 matches
Mail list logo
