Hello, Unfortunately, this was not a planned outage, so there's no way we could have warned about it in advance. Reports from users alerted us and allowed us to investigate and fix. In cases where there is a known error widely affecting the API, we do post on the forum, so that is a good idea to keep up to date.
We are also looking into other avenues to communicate these kinds of issues, as we know they can be pain points. Regards, Mike, AdWords API Team On Thursday, August 24, 2017 at 12:11:07 PM UTC-4, Mediative Reporting wrote: > > Hi Mike, > > Our reports completed successfully this morning. Thanks! > > There's one question my team wanted me to follow-up with you: > > Is there a system where we can be alerted on api issues like this to keep > updated? We've signed up to the Google Ads Developer blog RSS feed so we > do get updates for api release and sunset announcements, but failures like > this one were not mentioned there. > > Thanks again! > --Sheena. > > > > On Thursday, August 24, 2017 at 7:41:33 AM UTC-4, Michael Cloonan (AdWords > API Team) wrote: >> >> Hello, >> >> We pushed out a fix this morning that should allow you to retrieve your >> reports without error. Please let me know if you are still running into >> issues. >> >> Regards, >> Mike, AdWords API Team >> >> On Wednesday, August 23, 2017 at 6:36:48 AM UTC-4, Michael Cloonan >> (AdWords API Team) wrote: >>> >>> Hello, >>> >>> The team has made progress on determining the cause of this issue, but a >>> fix is still in progress. I will let you know as soon as I have more >>> information. >>> >>> Regards, >>> Mike, AdWords API Team >>> >>> On Wednesday, August 23, 2017 at 2:15:24 AM UTC-4, Mediative Reporting >>> wrote: >>>> >>>> Hello, is there any update on this issue? We're still getting *Internal >>>> Server Error* for those client accounts. >>>> >>>> >>>> >>>> On Thursday, August 17, 2017 at 11:43:53 AM UTC-4, Sreelakshmi >>>> Sasidharan (AdWords API Team) wrote: >>>>> >>>>> Hi Sheena, >>>>> >>>>> We are aware of this issue and currently our team is looking into >>>>> this. Could you please share the complete report definition, client >>>>> customer Id against which the report was run and the MCC ID your >>>>> developer >>>>> token is associated with? You could *Reply privately to the author* while >>>>> sharing the details. >>>>> >>>>> Thanks, >>>>> Sreelakshmi, AdWords API Team >>>>> >>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/775e8ceb-0bc6-4bc5-80f2-a8db45dc251c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
