For us, this problem affects the following countries: Argentina, Bolivia, Brazil, Chile, Costa Rica, Ecuador, Guatemala, Mexico and Puerto Rico. Other countries are good.
However, this only affects the report for 2009-10-18. For 10/19 and 10/20, reports are coming back correctly. We are going to skip 10/18 for now but we absolutely need the data. Here is a fragment of our report request for 10/19 (successful) - request id: 4f5ef39144e46c4850f0c76ec0dbd69b: <soapenv:Body> <scheduleReportJob xmlns="https://adwords.google.com/api/adwords/ v13"> <job xsi:type="ns7:DefinedReportJob" xmlns:ns7="https:// adwords.google.com/api/adwords/v13"> <crossClient xsi:type="xsd:boolean">false</crossClient> <endDay xsi:type="xsd:date">2009-10-19</endDay> <name xsi:type="xsd:string">Client READREPORT Report</name> <startDay xsi:type="xsd:date">2009-10-19</startDay> <aggregationTypes xsi:type="xsd:string">Daily</aggregationTypes> <campaigns xsi:type="xsd:int">43431364</campaigns> And here is fragment for 10/18 (failing) - request id: 3e6dfdba127a1779741ca943ae1fca8a <soapenv:Body> <scheduleReportJob xmlns="https://adwords.google.com/api/adwords/ v13"> <job xsi:type="ns7:DefinedReportJob" xmlns:ns7="https:// adwords.google.com/api/adwords/v13"> <crossClient xsi:type="xsd:boolean">false</crossClient> <endDay xsi:type="xsd:date">2009-10-18</endDay> <name xsi:type="xsd:string">Client READREPORT Report</name> <startDay xsi:type="xsd:date">2009-10-18</startDay> <aggregationTypes xsi:type="xsd:string">Daily</aggregationTypes> <campaigns xsi:type="xsd:int">43431364</campaigns> Henri On Oct 21, 9:16 am, Rachel <rac...@pildis.com> wrote: > After further investigation, this latest occurrence only affected our > Brazilian clients. The problem only occurred on 10/19 - on 10/20, we > were able to get reports for these clients again. > > cheers, > Rachel > > On Oct 20, 8:43 am, AdWords API Advisor <adwordsapiadvi...@google.com> > wrote: > > > Hi Henri and Rachel, > > > Unfortunately there hasn't been any updates from the core engineering > > team regarding the status of this issue, but I will reach out to them > > today to try and get more information. Thanks again for the feedback, > > and keep reporting in as you see this happen for other countries. > > > Best, > > - Eric > > > On Oct 19, 4:03 pm, Rachel <rac...@pildis.com> wrote: > > > > I am seeing the same sorts of errors starting today at 3 am US Central > > > Time when using scheduleReportJob. Previously, we saw this error on > > > 10/20/2008 at 3 am CT and 11/20/2008, also at 3 am CT. (Note that in > > > all cases, we weren't accessing the API between 12:30 am and 3 am CT.) > > > > The previous two times this resolved by the next day, but we also lost > > > a day's worth of data for our clients. > > > > cheers, > > > Rachel > > > > On Oct 13, 10:55 am, AdWords API Advisor > > > > <adwordsapiadvi...@google.com> wrote: > > > > Hi Manfred, > > > > > Thanks for the detailed information. Some of my colleagues have > > > > confirmed that there is an outstanding issue of date validation during > > > > daylight savings time transitions. I'll alert the core engineering > > > > team that users are still seeing this behavior. > > > > > Best, > > > > - Eric > > > > > On Oct 13, 8:24 am, manolator <scham...@gmail.com> wrote: > > > > > > Hi Eric, > > > > > > I'm sorry, we didn't log the request IDs of the validateReportJob. > > > > > But we just got the information from our germany sales contact, that > > > > > in Chile there was the switch to summer time on October 11th and the > > > > > same problem als occured with Argentinia on October 5th. > > > > > So the problem seems to be that these countries do the switch at > > > > > midnight. > > > > > > Best regards, > > > > > > Manfred > > > > > > On 12 Okt., 18:49, AdWords API Advisor <adwordsapiadvi...@google.com> > > > > > wrote: > > > > > > > Hi Manfred, > > > > > > > Do you have a request ID of a sample request that demonstrates this > > > > > > behavior? > > > > > > > Best, > > > > > > - Eric Koleda, AdWords API Team > > > > > > > On Oct 12, 11:59 am, manolator <scham...@gmail.com> wrote: > > > > > > > > Hi, > > > > > > > > since right after the maintenance downtime last weekend, we keep > > > > > > > getting error messages about a wrong datetime format when > > > > > > > requesting > > > > > > > keyword reports for two Chile based accounts. > > > > > > > Since several hundred different accounts from many different > > > > > > > countries > > > > > > > don't have any problem, perhaps something changed with the > > > > > > > maintenance > > > > > > > work? > > > > > > > > faultString: The day is in an unrecognized format. It must match > > > > > > > the > > > > > > > form YYYY-MM-DD with an optional timezone offset. > > > > > > > faultDetail: > > > > > > > {https://adwords.google.com/api/adwords/v13}fault: > > > > > > > <ns1:code>70</ns1:code> > > > > > > > <ns1:trigger>2009-10-11</ns1:trigger> > > > > > > > > Best regard, > > > > > > > > Manfred --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
