CampaignService - Error 70: The day is in an unrecognized format.

[Zweitze]

When calling CampaignService.getCampaignStats, this morning I got the
following error:

<detail>
<ns1:fault xmlns:ns1="https://adwords.google.com/api/adwords/
v12">
<ns1:code>70</ns1:code>

<ns1:message>The day is in an unrecognized format. It must
match the form YYYY-MM-DD with an optional timezone offset.</
ns1:message>

<ns1:trigger>2008-10-19</ns1:trigger>

</ns1:fault>

</detail>

RequestId: "e4a238e2af149ea325363c8de83ed77d"

Note the resemblance on
http://groups.google.com/group/adwords-api/browse_thread/thread/a1f0594782125389/b425bf7e44a339fc
although this is about the CampaignService.

This code runs for about three months on 40+ accounts, never saw this
problem before. Other accounts had no problem this morning.
Obviously the error message is wrong - but what was the problem? When
my code detects this problem, should it treat it like error 0 (=try
again in a few moments)?

Thanks in advance.

[AdWords API Advisor]

Hello,

It looks like the account being acted up in that request is in Sao
Paulo's time zone, and October 19 (like October 5 in the previous
example) is a date in which the daylight savings switchover takes
place. I'll add this report to the existing bug I have open.

The last I heard from the engineering team, they were exploring the
freshness of the time zone data being used by the AdWords API servers,
but I don't have any updates beyond that.

Cheers,
-Jeff Posnick, AdWords API Team

On Oct 20, 10:42 am, Zweitze <zwei...@gmail.com> wrote:
> When calling CampaignService.getCampaignStats, this morning I got the
> following error:
>
> <detail>
>       <ns1:fault xmlns:ns1="https://adwords.google.com/api/adwords/
> v12">
>        <ns1:code>70</ns1:code>
>
>        <ns1:message>The day is in an unrecognized format.  It must
> match the form YYYY-MM-DD with an optional timezone offset.</
> ns1:message>
>
>        <ns1:trigger>2008-10-19</ns1:trigger>
>
>     </ns1:fault>
>
>    </detail>
>
> RequestId: "e4a238e2af149ea325363c8de83ed77d"
>

> Note the resemblance onhttp://groups.google.com/group/adwords-api/browse_thread/thread/a1f05...

[Zweitze]

I assume this issue isn't fixed yet? It appeared again this morning,
same Brazilian account, same date (by coincidence)


RequestId: 220cac793f32da36c29a94616ef65526

<detail>
<ns1:fault xmlns:ns1="https://adwords.google.com/api/adwords/
v12">
<ns1:code>70</ns1:code>

<ns1:message>The day is in an unrecognized format. It must
match the form YYYY-MM-DD with an optional timezone offset.</
ns1:message>

<ns1:trigger>2008-10-19</ns1:trigger>

</ns1:fault>

</detail>

Thanks in advance.



On Oct 21, 7:29 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:

> Hello,
>
>  It looks like the account being acted up in that request is in Sao
> Paulo's time zone, and October 19 (like October 5 in the previous
> example) is a date in which the daylight savings switchover takes
> place. I'll add this report to the existing bug I have open.
>
>  The last I heard from the engineering team, they were exploring the
> freshness of the time zone data being used by the AdWords API servers,
> but I don't have any updates beyond that.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>

> On Oct 20, 10:42 am,Zweitze<zwei...@gmail.com> wrote:
>
>
>
> > When calling CampaignService.getCampaignStats, this morning I got the
> > following error:
>
> > <detail>
> >       <ns1:fault xmlns:ns1="https://adwords.google.com/api/adwords/
> > v12">
> >        <ns1:code>70</ns1:code>
>
> >        <ns1:message>The day is in an unrecognized format.  It must
> > match the form YYYY-MM-DD with an optional timezone offset.</
> > ns1:message>
>
> >        <ns1:trigger>2008-10-19</ns1:trigger>
>
> >     </ns1:fault>
>
> >    </detail>
>
> > RequestId: "e4a238e2af149ea325363c8de83ed77d"
>
> > Note the resemblance onhttp://groups.google.com/group/adwords-api/browse_thread/thread/a1f05...
> > although this is about the CampaignService.
>
> > This code runs for about three months on 40+ accounts, never saw this
> > problem before. Other accounts had no problem this morning.
> > Obviously the error message is wrong - but what was the problem? When
> > my code detects this problem, should it treat it like error 0 (=try
> > again in a few moments)?
>

> > Thanks in advance.- Hide quoted text -
>
> - Show quoted text -

[AdWords API Advisor]

Hello,

Unfortunately the issue is not resolved yet. The current thinking
from the core engineering team is that the root cause of the issue is
that midnight, Oct. 19 is not a valid time in that time zone (due to
daylight savings, clocks went directly from Oct. 18 23:59 to Oct. 19
01:00). I think it's more common for daylight savings time events to
take place at 01:00 instead of midnight in other time zones, which is
why this isn't a problem around the world twice a year.

I've been letting the folks responsible know that this is causing
issues for a number of our South American advertisers, but I can't
give any specific timeframe for when the server-side code will be
updated to work around this.

Cheers,
-Jeff Posnick, AdWords API Team