Hi Kevin, Thanks for sending the requestId. Unfortunately, I'm having trouble finding that request.
Would you mind sending the SOAP request and response XML *only to me* by clicking *Reply privately to author* on this post? Thanks, Josh, AdWords API Team On Thursday, May 21, 2015 at 3:56:06 PM UTC-4, Kevin Moritz wrote: > > I ran a bunch of API calls this afternoon and, as explained in Brian’s > response, was unable to see the sizeForSearch field in any of them. > > Here’s a request Id from one of the calls if it aids in the investigation. > 0005169ce42f71680aecae468100305c > > If I happen to make a call and return sizeForSearch I will note the > request Id > > Kevin > > On Thursday, May 21, 2015 at 2:28:55 PM UTC-5, Brian Moeskau wrote: >> >> Hi Josh, our job ran last night and every single request failed to return >> that field, so it seems like maybe the behavior simply changed, and the >> update was rolling out yesterday? Not sure if that's possible, but perhaps >> might explain the inconsistent behavior we were seeing. >> >> I've asked another dev on my team to see if we can still reproduce and >> send request ids if we can. >> >> Thanks, >> Brian >> >> On Thursday, May 21, 2015 at 2:21:54 PM UTC-5, Josh Radcliff (AdWords API >> Team) wrote: >>> >>> Hi Brian, >>> >>> Do you happen to have the *requestId* values from both a request that >>> returned null and one that did not return null for *sizeForSearch*? If >>> so, could you send them over so I can investigate? >>> >>> Thanks, >>> Josh, AdWords API Team >>> >>> On Wednesday, May 20, 2015 at 12:45:24 PM UTC-4, Brian Moeskau wrote: >>>> >>>> We've had an AdWords campaign report query in production for quite some >>>> time now, working great. Starting yesterday we began hitting null errors >>>> that we tracked down to the "sizeForSearch" field not being returned -- >>>> but >>>> this happens inconsistently from one call to the next for the exact same >>>> account / query. We've seen this on multiple accounts, with no rhyme or >>>> reason as to when a particular call might return that field or not. >>>> >>>> According to the docs this field *can* be null, and we added a check >>>> in our code to handle that, but I am concerned about the inconsistency of >>>> the behavior, and the fact that this just started happening after many >>>> months. This feels to me like a regression on the Google side, or at the >>>> very least a sudden change in expected behavior. Can anyone confirm this, >>>> and if it might affect other fields as well? >>>> >>>> Thanks, >>>> Brian >>>> >>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 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 --- 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 adwords-api+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/2b967063-355f-41f2-91b9-f0646adb581d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
