Problem with reports for accounts from Chile

[manolator]

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

[AdWords API Advisor]

Hi Manfred,

Do you have a request ID of a sample request that demonstrates this
behavior?

Best,
- Eric Koleda, AdWords API Team

[manolator]

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:

[AdWords API Advisor]

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

[h805]

Hi Eric,

Any news on this topic?
Since saturday, we are getting the same error for Chile and most other
latam countries. We are using V13.

Best,
Henri


On Oct 13, 8:55 am, AdWords API Advisor <adwordsapiadvi...@google.com>

[Rachel]

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

[AdWords API Advisor]

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

[Jay]

We're also seeing this. I hope Eric has some news soon.

Thx

On Oct 20, 9:43 am, AdWords API Advisor <adwordsapiadvi...@google.com>

[Rachel]

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>

[h805]

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

[h805]

Hi Eric,

We are still trying to get the reports for 10/18 and no luck, we are
getting the same error:

The day is in an unrecognized format. It must match the form
YYYY-MM-DD with an optional timezone offset.

Trigger: [2009-10-18]

Do you need more info?

Henri

[AdWords API Advisor]

Hi Henri,

Thank you for your patience on this issue. The core engineering team
is still actively working on a fix for this problem, but I don't have
any time estimates as to when it would be ready. Once I have more
information I'll update this thread.

Best,
- Eric

[AdWords API Advisor]

Hi All,

I apologize for the late update, but a fix has been deployed for this
issue and my tests indicate the problem is resolved. Let me know if
you run into any issues.

Best,
- Eric

On Oct 29, 12:28 pm, AdWords API Advisor