Hello, The bug that caused this issue has still not been fully addressed. Engineering is hard at work on getting that in as soon as possible. This means that it is possible (but very unlikely) that a job with operations moves into a DONE status, but erroneously shows that it has no operations or download URL. This is what happened on your previous job.
In this case, the job likely finished successfully, but is simply reporting its results incorrectly. The engineering team can force the job to update from the backend and show its correct state, which is what they did for the one job you had reported where this happened. If it happens again (hopefully it does not), let me know the job IDs and I can have engineering fix them as well. Otherwise, everything should be functioning normally. Regards, Mike, AdWords API Team On Tuesday, August 9, 2016 at 1:47:13 PM UTC-4, xtcsuk wrote: > > Hi Mike, > > Thank you, > > As for the old jobs, they are no longer valid, as the system has moved on > with new changes. > So, this has now been rectified, in case of a job with no operation, the > api will throw or something on upload, and will not move the job status > from pending to complete, right? > > regards, > Zia > > On Tuesday, 9 August 2016 18:28:08 UTC+1, Michael Cloonan (AdWords API > Team) wrote: >> >> Hello, >> >> The engineering team has taken a look at your account and only identified >> the single ID that you had already provided as being affected by that >> issue. If you check it again, it should have results and a download URL. >> >> Please let me know if this recurs with any future jobs. >> >> Regards, >> Mike, AdWords API Team >> >> On Monday, August 8, 2016 at 2:01:32 PM UTC-4, Michael Cloonan (AdWords >> API Team) wrote: >>> >>> Hello, >>> >>> The engineering team has confirmed that they are aware of a bug that can >>> put jobs into this state when they shouldn't be. They do have a process >>> they can perform on these "stuck" jobs to force them to return a correct >>> DownloadUrl. >>> >>> If you provide me with a complete list of jobs that have made their way >>> into this state, I can have engineering get them back on track for you. >>> >>> In the meanwhile, the team is working hard on getting a permanent fix in >>> place so this no longer happens going forward. >>> >>> Regards, >>> Mike, AdWords API Team >>> >>> On Monday, August 8, 2016 at 8:17:52 AM UTC-4, Michael Cloonan (AdWords >>> API Team) wrote: >>>> >>>> Hello, >>>> >>>> I apologize for the back and forth. I've contacted our engineering team >>>> to take a look at a specific job you provided and see if we can determine >>>> exactly what is going wrong from there. I'll let you know if I need more >>>> information from you or if I have any updates to share. >>>> >>>> Regards, >>>> Mike, AdWords API Team >>>> >>>> On Sunday, August 7, 2016 at 5:17:10 PM UTC-4, xtcsuk wrote: >>>>> >>>>> Thanks again for your reply. >>>>> >>>>> Based on our records that particular job should have contained at >>>>> least 173 operations. Our process in a nutshell, the system creates a >>>>> batch, which contains >=1 jobs, this particular job was part of a batch >>>>> which contained 218 jobs all of which finished with "Done" status and >>>>> with >>>>> N number of operation results except this one, this particular one as you >>>>> now know, has "Done" status with no operations. >>>>> >>>>> We have couple of more these instances, available upon request, >>>>> however, cannot easily get to log the upload operation for any scenarios >>>>> as >>>>> such, as said earlier this has happened/happens intermittently. >>>>> >>>>> On your side, would it be possible to clarify number of operations on >>>>> upload/active stages for the aforementioned job? >>>>> >>>>> regards, >>>>> Zia >>>>> >>>>> On Friday, 5 August 2016 17:29:57 UTC+1, Michael Cloonan (AdWords API >>>>> Team) wrote: >>>>>> >>>>>> Hello, >>>>>> >>>>>> Under normal circumstances, the job shouldn't move to Done unless >>>>>> some data has been provided and processed. That's why I'm so curious >>>>>> about >>>>>> what exactly made it into your request that allowed this to happen. >>>>>> >>>>>> Regards, >>>>>> Mike, AdWords API Team >>>>>> >>>>>> On Friday, August 5, 2016 at 11:03:35 AM UTC-4, xtcsuk wrote: >>>>>>> >>>>>>> Hi Mike, >>>>>>> >>>>>>> Thanks for the reply, our records show the job included some >>>>>>> operations, but do not have the log to provide you with, will try to >>>>>>> see if >>>>>>> we can do this. >>>>>>> In the meantime, is it possible for a job change status from Active >>>>>>> to Done with no operations attached to it? >>>>>>> >>>>>>> regards, >>>>>>> Zia >>>>>>> >>>>>>> On Friday, 5 August 2016 13:15:46 UTC+1, Michael Cloonan (AdWords >>>>>>> API Team) wrote: >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I took a look at the log you provided. It appears that in the case >>>>>>>> where the downloadUrl is omitted, there were also no operations >>>>>>>> performed, >>>>>>>> which means there would be no results to share via the downloadUrl >>>>>>>> anyway. >>>>>>>> Do you have logs of exactly what operations you uploaded for such a >>>>>>>> job? >>>>>>>> I'm not sure what would cause a job to kick off without having >>>>>>>> received any >>>>>>>> operations to perform, so I want to see if perhaps you're doing >>>>>>>> anything >>>>>>>> incorrect at that step in the process. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Mike, AdWords API Team >>>>>>>> >>>>>>>> On Friday, August 5, 2016 at 7:33:18 AM UTC-4, xtcsuk wrote: >>>>>>>>> >>>>>>>>> Hi Pete, >>>>>>>>> >>>>>>>>> We are still suffering from batchjobservice returning null >>>>>>>>> downloadUrl (intermittently) for a completed (done) job, sent you the >>>>>>>>> soap >>>>>>>>> (request/response) privately, just wondering if you have received it. >>>>>>>>> >>>>>>>>> regards, >>>>>>>>> Zia >>>>>>>>> >>>>>>>>> On Tuesday, 2 August 2016 04:09:00 UTC+1, Peter Oliquino wrote: >>>>>>>>>> >>>>>>>>>> Hi Zia, >>>>>>>>>> >>>>>>>>>> Feel free to contact us anytime if you encounter any issues. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Peter >>>>>>>>>> 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 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 https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/a032846b-b5b2-4595-aa15-1d61f82d671c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
