Hi Mike, Switching to v201101 will not necessarily resolve these problems, but there has been other BMJS issues in the past that have been due to v200909, so it may be worth investigating. Your solution on how to handle the failures sounds reasonable, and I'll talk to the core engineering team to see if there is anything else that can be done to reduce the likelihood of these errors. What is an example job ID that exhibited this behavior?
Best, - Eric Original Message Follows: ------------------------ From: Michael Lambert <mlamb...@merchantadvantage.com> Subject: FW: PAYLOAD_STORE_UNAVAILABLE - every time Date: Wed, 23 Mar 2011 10:52:22 -0500 > Hi Erik – > Thank you for the follow up. > > Not all of our transactions are being reported as Lost or Unprocessed, but > all bulk jobs in excess of 4000 records seems to be the breaking point – also > only ads and criteria –adgroups never seem to fail. We are using v200909 but > have been successfully using this version of Google and our code for a few > months – but only started getting these errors over the last week or so. > > The solution we’re currently working on is to continue trying our Bulk job > until we begin to get the Lost or Unprocessed – then re-try Unprocessed using > the individual processing instead of the bulk, and re-requesting the ad and > criteria ID’s for the lost ads and keywords individually using a get (since > it’s new we’re going to develop this service in v201101. > > So – are you saying this issue would not occur if we migrated to v201101 for > BulkMutate? Obviously we need to do that migration at some point anyway. > > Thanks again for your help, > Mike > > From: Eric Koleda [mailto:eric.kol...@google.com] > Sent: Wednesday, March 23, 2011 11:24 AM > To: adwords-api@googlegroups.com > Cc: API2Go > Subject: Re: PAYLOAD_STORE_UNAVAILABLE - every time > > Hi API2Go, > > Are all operations in your job being reported as Lost or Unprocessed, or only > some of them? There is a known error with the BMJS in v200909 around bad geo > targets, although switching to v201003 or later should resolve that issue. > > Best, > - Eric Koleda, AdWords API Team > -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
