Interesting point.
In the last 2 days, we incurred ~250,000 quota unit costs for batches
of work which did not process through to completion because of a "503"
error.
The API quota cost displayed via our MCC accounts correlates pretty
closely with our own logging (99.6%) - indicating that no allowance
has been made for the technical problems we've been experiencing.
pete
On Sep 15, 10:50 am, David Levy <dvid.l...@gmail.com> wrote:
> Don't you think it's related to the maintenance on 12/09 ?
> It seems that the errors occured after it ...
>
> This morning, I think 5 to 10% of my requests are failing.
>
> My question to Eric : Do Google charge us for these failed
> requests ?! That would be really unfair.
>
> On 15 sep, 12:19, pete <peteseri...@gmail.com> wrote:
>
>
>
> > Hi Eric
>
> > As of 0900GMT, 100% of our Structure report requests are failing...
>
> > pete
>
> > On Sep 14, 8:43 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
> > wrote:
>
> > > All,
>
> > > The core engineering team has resolved the issue and it looks like the
> > > errors have stopped. If you continue to receive these errors please
> > > let me know.
>
> > > Best,
> > > - Eric
>
> > > On Sep 14, 10:38 am, AdWords API Advisor
>
> > > <adwordsapiadvi...@google.com> wrote:
> > > > All,
>
> > > > Thank you for bringing this to our attention and for detailed
> > > > technical information. The core engineering team is aware of the
> > > > issue and working towards a resolution. I'll update this thread once
> > > > I have more information.
>
> > > > Best,
> > > > - Eric Koleda, AdWords API Team
>
> > > > On Sep 14, 10:07 am, "[RV] Colin" <cmut...@redventures.com> wrote:
>
> > > > > We've seen this error consistently since 3:15 AM EST today...showing
> > > > > no signs of stopping. Same "503 Service Unavailable" when going to
> > > > > retrieve a scheduled report. Things seemed to all start acting
> > > > > strangely on Saturday, when the system was taken down for
> > > > > maintenance. But now we can't get any data to come through. We are
> > > > > using the APIlity connectors on our side, with no change to them
> > > > > whatsoever.
>
> > > > > We can do other things just fine (e.g. change keyword/adgroup
> > > > > information via CriterionService). So we think it may be limited to a
> > > > > report creating/scheduling/downloading issue.
>
> > > > > Any word from the API team?
>
> > > > > On Sep 14, 9:47 am, "j.e.frank" <j.e.fr...@gmail.com> wrote:
>
> > > > > > I'm also seeing the "503 Service Unavailable" error quite frequently
> > > > > > this morning. It is not consistent, but I would say it happens
> > > > > > about
> > > > > > 2/3 of the time, when I'm trying to create or download a report.
> > > > > > I'm
> > > > > > using the Java client library (v13).
>
> > > > > > On Sep 14, 6:52 am, David Levy <dvid.l...@gmail.com> wrote:
>
> > > > > > > I also have errors since this morning, like :
>
> > > > > > > File "/libs/aw_api/AdGroupService.py", line 296, in
> > > > > > > GetAllAdGroups
> > > > > > > 'AdGroup', self.__loc, request)
> > > > > > > File "/libs/aw_api/WebService.py", line 291, in CallMethod
> > > > > > > if 'data' in error and not buf.IsHandshakeComplete():
> > > > > > > File "/libs/aw_api/SoapBuffer.py", line 153, in
> > > > > > > IsHandshakeComplete
> > > > > > > if (self.GetHeadersOut() and self.GetSOAPOut() and
> > > > > > > self.GetHeadersIn() and
> > > > > > > File "/libs/aw_api/SoapBuffer.py", line 261, in GetHeadersOut
> > > > > > > return self.__GetDumpValue('dumpHeadersOut')
> > > > > > > File "/libs/aw_api/SoapBuffer.py", line 250, in __GetDumpValue
> > > > > > > dump_value = self.__GetBufferAsDict()[dump_type]
> > > > > > > File "/libs/aw_api/SoapBuffer.py", line 181, in
> > > > > > > __GetBufferAsDict
> > > > > > > xml_out = self.__PrettyPrintXml(xml_out, 1)
> > > > > > > File "/libs/aw_api/SoapBuffer.py", line 682, in __PrettyPrintXml
> > > > > > > dom = minidom.parseString(doc)
> > > > > > > File
> > > > > > > "/usr/virtualenv1/lib/python2.5/site-packages/PyXML-0.8.4-py2.5-
> > > > > > > linux-x86_64.egg/_xmlplus/dom/minidom.py", line 1925, in
> > > > > > > parseString
> > > > > > > return expatbuilder.parseString(string)
> > > > > > > File
> > > > > > > "/usr/virtualenv1/lib/python2.5/site-packages/PyXML-0.8.4-py2.5-
> > > > > > > linux-x86_64.egg/_xmlplus/dom/expatbuilder.py", line 942, in
> > > > > > > parseString
> > > > > > > return builder.parseString(string)
> > > > > > > File
> > > > > > > "/usr/virtualenv1/lib/python2.5/site-packages/PyXML-0.8.4-py2.5-
> > > > > > > linux-x86_64.egg/_xmlplus/dom/expatbuilder.py", line 223, in
> > > > > > > parseString
> > > > > > > parser.Parse(string, True)
> > > > > > > ExpatError: syntax error: line 2, column 0
>
> > > > > > > How can we fix this ?
>
> > > > > > > On 14 sep, 13:40, DavM <dmidg...@gmail.com> wrote:
>
> > > > > > > > We've been seeing these errors with increasing regularity on a
> > > > > > > > variety
> > > > > > > > of requests since 08:00 GMT this morning...
>
> > > > > > > > David
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
-~----------~----~----~----~------~----~------~--~---
