Re: api version 201605 - batchjobservice

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Zia,

Are you still experiencing problems with batch jobs? We've been rolling out 
improvements over the last month and have seen the number of problematic 
jobs continue to decrease, so I'm curious how things are looking from your 
side.

Thanks,
Josh, AdWords API Team

On Monday, September 19, 2016 at 12:33:42 PM UTC-4, xtcsuk wrote:
>
> Hi Josh,
>
> Thanks for the update, however, i have to say the problem still persists 
> for some jobs, hoping for a complete resolution soon.
>
> regards,
> Zia
>
> On Friday, 9 September 2016 18:44:00 UTC+1, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Zia,
>>
>> Several changes rolled out this week to improve the reliability of 
>> *BatchJobService*, and we've seen a significant drop in the # of jobs 
>> with missing *downloadUrl*s. I expect to see more improvements over the 
>> coming weeks as well.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, August 25, 2016 at 8:15:05 AM UTC-4, xtcsuk wrote:
>>>
>>> Thanks Josh, much appreciated.
>>>
>>> regards,
>>> Zia
>>>
>>> On Wednesday, 24 August 2016 21:22:35 UTC+1, Josh Radcliff (AdWords API 
>>> Team) wrote:

 Hi Zia,

 Thanks for the feedback. I realize this is an important issue for 
 everyone migrating to BatchJobService. I'll be sure to update this post as 
 improvements roll out.

 Best regards,
 Josh, AdWords API Team

 On Wednesday, August 24, 2016 at 6:49:00 AM UTC-4, xtcsuk wrote:
>
> Hi Josh,
>
> Thank you for your help, as for this particular operation, the job is 
> no longer valid (our side), because the subsequent pushes will have 
> invalidated/overwritten it.  It is of vital importance, the underlying 
> issue (api side) is addressed asap, by the time the issue is resolved 
> that 
> job is no longer valid.
>
> Now, that we have the sunset on api v201601 approaching fast, we are 
> on v201605, can't rollback.  The problem in this thread as well as this 
> api 
> version 201605 
> , tells 
> us the batchjobservice is not 100% reliable, the sooner we have the fix 
> the 
> better.
>
> regards,
> Zia
>
> On Tuesday, 23 August 2016 19:00:51 UTC+1, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Zia,
>>
>> The *downloadUrl* has been regenerated for that job. Please get the 
>> *downloadUrl* from *BatchJobService* again and try to download 
>> results.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Tuesday, August 23, 2016 at 9:40:16 AM UTC-4, Josh Radcliff 
>> (AdWords API Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> I just asked for an update on that job. I'll reply back here as soon 
>>> as I have more information.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, August 23, 2016 at 6:32:11 AM UTC-4, xtcsuk wrote:

 Hi Thanet,

 Any luck with this issue, as instructed, posted the requested info 
 a few days ago, hope you have got it.

 regards,
 Zia

 On Thursday, 18 August 2016 03:59:53 UTC+1, Thanet Knack 
 Praneenararat (AdWords API Team) wrote:
>
> Hello Zia,
>
> I'll handle this case instead of Josh.
> It's fine to post in this thread again, but would be more easy for 
> you to track the answers if you create another thread instead.
>
> For this case, could you please pass me your download URL as well 
> using *Reply privately to author*?
> I saw some of the results partially executed already, so there 
> might be a problem of download URL.
>
> Cheers,
> Thanet, AdWords API Team
>
> On Thursday, August 18, 2016 at 1:39:04 AM UTC+9, xtcsuk wrote:
>>
>> Hey Josh,
>>
>> Its me again, this time a different issue, was not sure to create 
>> a new thread, so here it goes:
>>
>> The job:
>>
>> job id   account id
>> 344573194   1011654677
>>
>> has a "CANCELLED" status with a downloadUrl assigned to it, but 
>> on get the results, it throws 404, may be another bug?
>>
>> regards,
>> Zia
>>
>> On Wednesday, 17 August 2016 11:48:37 UTC+1, xtcsuk wrote:
>>>
>>> Hi Josh,
>>>
>>> Thank you for the clarification, on our side, however, as you 
>>> can imagine, we have logic to compare the two (upload/result) to 
>>> marry up 
>>> the operation results.  So, if the numbers do not match, it just 
>>> simply 
>>> don't work.
>>> Firstly, hoping for this not happen again (permanent fix), will 
>>> keep an eye and if so will come back to 

Re: api version 201605 - batchjobservice

[xtcsuk]

Hi Josh,

Thanks for the update, however, i have to say the problem still persists 
for some jobs, hoping for a complete resolution soon.

regards,
Zia

On Friday, 9 September 2016 18:44:00 UTC+1, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Zia,
>
> Several changes rolled out this week to improve the reliability of 
> *BatchJobService*, and we've seen a significant drop in the # of jobs 
> with missing *downloadUrl*s. I expect to see more improvements over the 
> coming weeks as well.
>
> Thanks,
> Josh, AdWords API Team
>
> On Thursday, August 25, 2016 at 8:15:05 AM UTC-4, xtcsuk wrote:
>>
>> Thanks Josh, much appreciated.
>>
>> regards,
>> Zia
>>
>> On Wednesday, 24 August 2016 21:22:35 UTC+1, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> Thanks for the feedback. I realize this is an important issue for 
>>> everyone migrating to BatchJobService. I'll be sure to update this post as 
>>> improvements roll out.
>>>
>>> Best regards,
>>> Josh, AdWords API Team
>>>
>>> On Wednesday, August 24, 2016 at 6:49:00 AM UTC-4, xtcsuk wrote:

 Hi Josh,

 Thank you for your help, as for this particular operation, the job is 
 no longer valid (our side), because the subsequent pushes will have 
 invalidated/overwritten it.  It is of vital importance, the underlying 
 issue (api side) is addressed asap, by the time the issue is resolved that 
 job is no longer valid.

 Now, that we have the sunset on api v201601 approaching fast, we are on 
 v201605, can't rollback.  The problem in this thread as well as this api 
 version 201605 
 , tells 
 us the batchjobservice is not 100% reliable, the sooner we have the fix 
 the 
 better.

 regards,
 Zia

 On Tuesday, 23 August 2016 19:00:51 UTC+1, Josh Radcliff (AdWords API 
 Team) wrote:
>
> Hi Zia,
>
> The *downloadUrl* has been regenerated for that job. Please get the 
> *downloadUrl* from *BatchJobService* again and try to download 
> results.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, August 23, 2016 at 9:40:16 AM UTC-4, Josh Radcliff 
> (AdWords API Team) wrote:
>>
>> Hi Zia,
>>
>> I just asked for an update on that job. I'll reply back here as soon 
>> as I have more information.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Tuesday, August 23, 2016 at 6:32:11 AM UTC-4, xtcsuk wrote:
>>>
>>> Hi Thanet,
>>>
>>> Any luck with this issue, as instructed, posted the requested info a 
>>> few days ago, hope you have got it.
>>>
>>> regards,
>>> Zia
>>>
>>> On Thursday, 18 August 2016 03:59:53 UTC+1, Thanet Knack 
>>> Praneenararat (AdWords API Team) wrote:

 Hello Zia,

 I'll handle this case instead of Josh.
 It's fine to post in this thread again, but would be more easy for 
 you to track the answers if you create another thread instead.

 For this case, could you please pass me your download URL as well 
 using *Reply privately to author*?
 I saw some of the results partially executed already, so there 
 might be a problem of download URL.

 Cheers,
 Thanet, AdWords API Team

 On Thursday, August 18, 2016 at 1:39:04 AM UTC+9, xtcsuk wrote:
>
> Hey Josh,
>
> Its me again, this time a different issue, was not sure to create 
> a new thread, so here it goes:
>
> The job:
>
> job id   account id
> 344573194   1011654677
>
> has a "CANCELLED" status with a downloadUrl assigned to it, but on 
> get the results, it throws 404, may be another bug?
>
> regards,
> Zia
>
> On Wednesday, 17 August 2016 11:48:37 UTC+1, xtcsuk wrote:
>>
>> Hi Josh,
>>
>> Thank you for the clarification, on our side, however, as you can 
>> imagine, we have logic to compare the two (upload/result) to marry 
>> up the 
>> operation results.  So, if the numbers do not match, it just simply 
>> don't 
>> work.
>> Firstly, hoping for this not happen again (permanent fix), will 
>> keep an eye and if so will come back to you.
>>
>> regards,
>> Zia
>>
>> On Tuesday, 16 August 2016 19:06:50 UTC+1, Josh Radcliff (AdWords 
>> API Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> The count mismatch is an artifact of the failed download URL 
>>> generation. You can safely ignore the mismatch (in this particular 
>>> case) 
>>> when processing the results from the URL.
>>>
>>> Thanks,
>>> Josh, AdWords API Team

Re: api version 201605 - batchjobservice

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Zia,

Several changes rolled out this week to improve the reliability of 
*BatchJobService*, and we've seen a significant drop in the # of jobs with 
missing *downloadUrl*s. I expect to see more improvements over the coming 
weeks as well.

Thanks,
Josh, AdWords API Team

On Thursday, August 25, 2016 at 8:15:05 AM UTC-4, xtcsuk wrote:
>
> Thanks Josh, much appreciated.
>
> regards,
> Zia
>
> On Wednesday, 24 August 2016 21:22:35 UTC+1, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Zia,
>>
>> Thanks for the feedback. I realize this is an important issue for 
>> everyone migrating to BatchJobService. I'll be sure to update this post as 
>> improvements roll out.
>>
>> Best regards,
>> Josh, AdWords API Team
>>
>> On Wednesday, August 24, 2016 at 6:49:00 AM UTC-4, xtcsuk wrote:
>>>
>>> Hi Josh,
>>>
>>> Thank you for your help, as for this particular operation, the job is no 
>>> longer valid (our side), because the subsequent pushes will have 
>>> invalidated/overwritten it.  It is of vital importance, the underlying 
>>> issue (api side) is addressed asap, by the time the issue is resolved that 
>>> job is no longer valid.
>>>
>>> Now, that we have the sunset on api v201601 approaching fast, we are on 
>>> v201605, can't rollback.  The problem in this thread as well as this api 
>>> version 201605 
>>> , tells 
>>> us the batchjobservice is not 100% reliable, the sooner we have the fix the 
>>> better.
>>>
>>> regards,
>>> Zia
>>>
>>> On Tuesday, 23 August 2016 19:00:51 UTC+1, Josh Radcliff (AdWords API 
>>> Team) wrote:

 Hi Zia,

 The *downloadUrl* has been regenerated for that job. Please get the 
 *downloadUrl* from *BatchJobService* again and try to download results.

 Thanks,
 Josh, AdWords API Team

 On Tuesday, August 23, 2016 at 9:40:16 AM UTC-4, Josh Radcliff (AdWords 
 API Team) wrote:
>
> Hi Zia,
>
> I just asked for an update on that job. I'll reply back here as soon 
> as I have more information.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, August 23, 2016 at 6:32:11 AM UTC-4, xtcsuk wrote:
>>
>> Hi Thanet,
>>
>> Any luck with this issue, as instructed, posted the requested info a 
>> few days ago, hope you have got it.
>>
>> regards,
>> Zia
>>
>> On Thursday, 18 August 2016 03:59:53 UTC+1, Thanet Knack 
>> Praneenararat (AdWords API Team) wrote:
>>>
>>> Hello Zia,
>>>
>>> I'll handle this case instead of Josh.
>>> It's fine to post in this thread again, but would be more easy for 
>>> you to track the answers if you create another thread instead.
>>>
>>> For this case, could you please pass me your download URL as well 
>>> using *Reply privately to author*?
>>> I saw some of the results partially executed already, so there might 
>>> be a problem of download URL.
>>>
>>> Cheers,
>>> Thanet, AdWords API Team
>>>
>>> On Thursday, August 18, 2016 at 1:39:04 AM UTC+9, xtcsuk wrote:

 Hey Josh,

 Its me again, this time a different issue, was not sure to create a 
 new thread, so here it goes:

 The job:

 job id   account id
 344573194   1011654677

 has a "CANCELLED" status with a downloadUrl assigned to it, but on 
 get the results, it throws 404, may be another bug?

 regards,
 Zia

 On Wednesday, 17 August 2016 11:48:37 UTC+1, xtcsuk wrote:
>
> Hi Josh,
>
> Thank you for the clarification, on our side, however, as you can 
> imagine, we have logic to compare the two (upload/result) to marry up 
> the 
> operation results.  So, if the numbers do not match, it just simply 
> don't 
> work.
> Firstly, hoping for this not happen again (permanent fix), will 
> keep an eye and if so will come back to you.
>
> regards,
> Zia
>
> On Tuesday, 16 August 2016 19:06:50 UTC+1, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Zia,
>>
>> The count mismatch is an artifact of the failed download URL 
>> generation. You can safely ignore the mismatch (in this particular 
>> case) 
>> when processing the results from the URL.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, August 15, 2016 at 11:39:45 AM UTC-4, Josh Radcliff 
>> (AdWords API Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> I'm looking into that one and will get back to you with an 
>>> update.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, August 15, 2016 at 9:08:56 AM UTC-4, xtcsuk 

Re: api version 201605 - batchjobservice

[xtcsuk]

Thanks Josh, much appreciated.

regards,
Zia

On Wednesday, 24 August 2016 21:22:35 UTC+1, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Zia,
>
> Thanks for the feedback. I realize this is an important issue for everyone 
> migrating to BatchJobService. I'll be sure to update this post as 
> improvements roll out.
>
> Best regards,
> Josh, AdWords API Team
>
> On Wednesday, August 24, 2016 at 6:49:00 AM UTC-4, xtcsuk wrote:
>>
>> Hi Josh,
>>
>> Thank you for your help, as for this particular operation, the job is no 
>> longer valid (our side), because the subsequent pushes will have 
>> invalidated/overwritten it.  It is of vital importance, the underlying 
>> issue (api side) is addressed asap, by the time the issue is resolved that 
>> job is no longer valid.
>>
>> Now, that we have the sunset on api v201601 approaching fast, we are on 
>> v201605, can't rollback.  The problem in this thread as well as this api 
>> version 201605 
>> , tells 
>> us the batchjobservice is not 100% reliable, the sooner we have the fix the 
>> better.
>>
>> regards,
>> Zia
>>
>> On Tuesday, 23 August 2016 19:00:51 UTC+1, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> The *downloadUrl* has been regenerated for that job. Please get the 
>>> *downloadUrl* from *BatchJobService* again and try to download results.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, August 23, 2016 at 9:40:16 AM UTC-4, Josh Radcliff (AdWords 
>>> API Team) wrote:

 Hi Zia,

 I just asked for an update on that job. I'll reply back here as soon as 
 I have more information.

 Thanks,
 Josh, AdWords API Team

 On Tuesday, August 23, 2016 at 6:32:11 AM UTC-4, xtcsuk wrote:
>
> Hi Thanet,
>
> Any luck with this issue, as instructed, posted the requested info a 
> few days ago, hope you have got it.
>
> regards,
> Zia
>
> On Thursday, 18 August 2016 03:59:53 UTC+1, Thanet Knack Praneenararat 
> (AdWords API Team) wrote:
>>
>> Hello Zia,
>>
>> I'll handle this case instead of Josh.
>> It's fine to post in this thread again, but would be more easy for 
>> you to track the answers if you create another thread instead.
>>
>> For this case, could you please pass me your download URL as well 
>> using *Reply privately to author*?
>> I saw some of the results partially executed already, so there might 
>> be a problem of download URL.
>>
>> Cheers,
>> Thanet, AdWords API Team
>>
>> On Thursday, August 18, 2016 at 1:39:04 AM UTC+9, xtcsuk wrote:
>>>
>>> Hey Josh,
>>>
>>> Its me again, this time a different issue, was not sure to create a 
>>> new thread, so here it goes:
>>>
>>> The job:
>>>
>>> job id   account id
>>> 344573194   1011654677
>>>
>>> has a "CANCELLED" status with a downloadUrl assigned to it, but on 
>>> get the results, it throws 404, may be another bug?
>>>
>>> regards,
>>> Zia
>>>
>>> On Wednesday, 17 August 2016 11:48:37 UTC+1, xtcsuk wrote:

 Hi Josh,

 Thank you for the clarification, on our side, however, as you can 
 imagine, we have logic to compare the two (upload/result) to marry up 
 the 
 operation results.  So, if the numbers do not match, it just simply 
 don't 
 work.
 Firstly, hoping for this not happen again (permanent fix), will 
 keep an eye and if so will come back to you.

 regards,
 Zia

 On Tuesday, 16 August 2016 19:06:50 UTC+1, Josh Radcliff (AdWords 
 API Team) wrote:
>
> Hi Zia,
>
> The count mismatch is an artifact of the failed download URL 
> generation. You can safely ignore the mismatch (in this particular 
> case) 
> when processing the results from the URL.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, August 15, 2016 at 11:39:45 AM UTC-4, Josh Radcliff 
> (AdWords API Team) wrote:
>>
>> Hi Zia,
>>
>> I'm looking into that one and will get back to you with an update.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, August 15, 2016 at 9:08:56 AM UTC-4, xtcsuk wrote:
>>>
>>> Hi Josh,
>>>
>>> Thanks again, sorry my mistake.  
>>>
>>> On this subject, this is a job details where we have a 
>>> discrepancy in between the number of operations uploaded and number 
>>> of 
>>> operations executed:
>>>
>>> job idaccount id
>>> 342115475 7653799969
>>>
>>> our application is limited to assign maximum 3 number of 
>>> 

Re: api version 201605 - batchjobservice

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Zia,

Thanks for the feedback. I realize this is an important issue for everyone 
migrating to BatchJobService. I'll be sure to update this post as 
improvements roll out.

Best regards,
Josh, AdWords API Team

On Wednesday, August 24, 2016 at 6:49:00 AM UTC-4, xtcsuk wrote:
>
> Hi Josh,
>
> Thank you for your help, as for this particular operation, the job is no 
> longer valid (our side), because the subsequent pushes will have 
> invalidated/overwritten it.  It is of vital importance, the underlying 
> issue (api side) is addressed asap, by the time the issue is resolved that 
> job is no longer valid.
>
> Now, that we have the sunset on api v201601 approaching fast, we are on 
> v201605, can't rollback.  The problem in this thread as well as this api 
> version 201605 
> , tells 
> us the batchjobservice is not 100% reliable, the sooner we have the fix the 
> better.
>
> regards,
> Zia
>
> On Tuesday, 23 August 2016 19:00:51 UTC+1, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Zia,
>>
>> The *downloadUrl* has been regenerated for that job. Please get the 
>> *downloadUrl* from *BatchJobService* again and try to download results.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Tuesday, August 23, 2016 at 9:40:16 AM UTC-4, Josh Radcliff (AdWords 
>> API Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> I just asked for an update on that job. I'll reply back here as soon as 
>>> I have more information.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, August 23, 2016 at 6:32:11 AM UTC-4, xtcsuk wrote:

 Hi Thanet,

 Any luck with this issue, as instructed, posted the requested info a 
 few days ago, hope you have got it.

 regards,
 Zia

 On Thursday, 18 August 2016 03:59:53 UTC+1, Thanet Knack Praneenararat 
 (AdWords API Team) wrote:
>
> Hello Zia,
>
> I'll handle this case instead of Josh.
> It's fine to post in this thread again, but would be more easy for you 
> to track the answers if you create another thread instead.
>
> For this case, could you please pass me your download URL as well 
> using *Reply privately to author*?
> I saw some of the results partially executed already, so there might 
> be a problem of download URL.
>
> Cheers,
> Thanet, AdWords API Team
>
> On Thursday, August 18, 2016 at 1:39:04 AM UTC+9, xtcsuk wrote:
>>
>> Hey Josh,
>>
>> Its me again, this time a different issue, was not sure to create a 
>> new thread, so here it goes:
>>
>> The job:
>>
>> job id   account id
>> 344573194   1011654677
>>
>> has a "CANCELLED" status with a downloadUrl assigned to it, but on 
>> get the results, it throws 404, may be another bug?
>>
>> regards,
>> Zia
>>
>> On Wednesday, 17 August 2016 11:48:37 UTC+1, xtcsuk wrote:
>>>
>>> Hi Josh,
>>>
>>> Thank you for the clarification, on our side, however, as you can 
>>> imagine, we have logic to compare the two (upload/result) to marry up 
>>> the 
>>> operation results.  So, if the numbers do not match, it just simply 
>>> don't 
>>> work.
>>> Firstly, hoping for this not happen again (permanent fix), will keep 
>>> an eye and if so will come back to you.
>>>
>>> regards,
>>> Zia
>>>
>>> On Tuesday, 16 August 2016 19:06:50 UTC+1, Josh Radcliff (AdWords 
>>> API Team) wrote:

 Hi Zia,

 The count mismatch is an artifact of the failed download URL 
 generation. You can safely ignore the mismatch (in this particular 
 case) 
 when processing the results from the URL.

 Thanks,
 Josh, AdWords API Team

 On Monday, August 15, 2016 at 11:39:45 AM UTC-4, Josh Radcliff 
 (AdWords API Team) wrote:
>
> Hi Zia,
>
> I'm looking into that one and will get back to you with an update.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, August 15, 2016 at 9:08:56 AM UTC-4, xtcsuk wrote:
>>
>> Hi Josh,
>>
>> Thanks again, sorry my mistake.  
>>
>> On this subject, this is a job details where we have a 
>> discrepancy in between the number of operations uploaded and number 
>> of 
>> operations executed:
>>
>> job idaccount id
>> 342115475 7653799969
>>
>> our application is limited to assign maximum 3 number of 
>> operations per job, so this job in our end has 3 operations, 
>> however 
>> the api results look different containing 5 number of operations.
>>
>> Appreciating the verification on this one, please.
>>
>> regards,
>> Zia
>>

Re: api version 201605 - batchjobservice

[xtcsuk]

Hi Josh,

Thank you for your help, as for this particular operation, the job is no 
longer valid (our side), because the subsequent pushes will have 
invalidated/overwritten it.  It is of vital importance, the underlying 
issue (api side) is addressed asap, by the time the issue is resolved that 
job is no longer valid.

Now, that we have the sunset on api v201601 approaching fast, we are on 
v201605, can't rollback.  The problem in this thread as well as this api 
version 201605 
, tells us 
the batchjobservice is not 100% reliable, the sooner we have the fix the 
better.

regards,
Zia

On Tuesday, 23 August 2016 19:00:51 UTC+1, Josh Radcliff (AdWords API Team) 
wrote:
>
> Hi Zia,
>
> The *downloadUrl* has been regenerated for that job. Please get the 
> *downloadUrl* from *BatchJobService* again and try to download results.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, August 23, 2016 at 9:40:16 AM UTC-4, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Zia,
>>
>> I just asked for an update on that job. I'll reply back here as soon as I 
>> have more information.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Tuesday, August 23, 2016 at 6:32:11 AM UTC-4, xtcsuk wrote:
>>>
>>> Hi Thanet,
>>>
>>> Any luck with this issue, as instructed, posted the requested info a few 
>>> days ago, hope you have got it.
>>>
>>> regards,
>>> Zia
>>>
>>> On Thursday, 18 August 2016 03:59:53 UTC+1, Thanet Knack Praneenararat 
>>> (AdWords API Team) wrote:

 Hello Zia,

 I'll handle this case instead of Josh.
 It's fine to post in this thread again, but would be more easy for you 
 to track the answers if you create another thread instead.

 For this case, could you please pass me your download URL as well using 
 *Reply 
 privately to author*?
 I saw some of the results partially executed already, so there might be 
 a problem of download URL.

 Cheers,
 Thanet, AdWords API Team

 On Thursday, August 18, 2016 at 1:39:04 AM UTC+9, xtcsuk wrote:
>
> Hey Josh,
>
> Its me again, this time a different issue, was not sure to create a 
> new thread, so here it goes:
>
> The job:
>
> job id   account id
> 344573194   1011654677
>
> has a "CANCELLED" status with a downloadUrl assigned to it, but on get 
> the results, it throws 404, may be another bug?
>
> regards,
> Zia
>
> On Wednesday, 17 August 2016 11:48:37 UTC+1, xtcsuk wrote:
>>
>> Hi Josh,
>>
>> Thank you for the clarification, on our side, however, as you can 
>> imagine, we have logic to compare the two (upload/result) to marry up 
>> the 
>> operation results.  So, if the numbers do not match, it just simply 
>> don't 
>> work.
>> Firstly, hoping for this not happen again (permanent fix), will keep 
>> an eye and if so will come back to you.
>>
>> regards,
>> Zia
>>
>> On Tuesday, 16 August 2016 19:06:50 UTC+1, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> The count mismatch is an artifact of the failed download URL 
>>> generation. You can safely ignore the mismatch (in this particular 
>>> case) 
>>> when processing the results from the URL.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, August 15, 2016 at 11:39:45 AM UTC-4, Josh Radcliff 
>>> (AdWords API Team) wrote:

 Hi Zia,

 I'm looking into that one and will get back to you with an update.

 Thanks,
 Josh, AdWords API Team

 On Monday, August 15, 2016 at 9:08:56 AM UTC-4, xtcsuk wrote:
>
> Hi Josh,
>
> Thanks again, sorry my mistake.  
>
> On this subject, this is a job details where we have a discrepancy 
> in between the number of operations uploaded and number of operations 
> executed:
>
> job idaccount id
> 342115475 7653799969
>
> our application is limited to assign maximum 3 number of 
> operations per job, so this job in our end has 3 operations, 
> however 
> the api results look different containing 5 number of operations.
>
> Appreciating the verification on this one, please.
>
> regards,
> Zia
>
> On Monday, 15 August 2016 13:39:21 UTC+1, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Zia,
>>
>> The job I was referring to was batch job ID 341175452, which had 
>> status of CANCELED (please see your first email on this post). The 
>> current 
>> status remains as CANCELED.
>>
>> 
>>   341175452
>>   CANCELED

Re: api version 201605 - batchjobservice

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Zia,

The *downloadUrl* has been regenerated for that job. Please get the 
*downloadUrl* from *BatchJobService* again and try to download results.

Thanks,
Josh, AdWords API Team

On Tuesday, August 23, 2016 at 9:40:16 AM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Zia,
>
> I just asked for an update on that job. I'll reply back here as soon as I 
> have more information.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, August 23, 2016 at 6:32:11 AM UTC-4, xtcsuk wrote:
>>
>> Hi Thanet,
>>
>> Any luck with this issue, as instructed, posted the requested info a few 
>> days ago, hope you have got it.
>>
>> regards,
>> Zia
>>
>> On Thursday, 18 August 2016 03:59:53 UTC+1, Thanet Knack Praneenararat 
>> (AdWords API Team) wrote:
>>>
>>> Hello Zia,
>>>
>>> I'll handle this case instead of Josh.
>>> It's fine to post in this thread again, but would be more easy for you 
>>> to track the answers if you create another thread instead.
>>>
>>> For this case, could you please pass me your download URL as well using 
>>> *Reply 
>>> privately to author*?
>>> I saw some of the results partially executed already, so there might be 
>>> a problem of download URL.
>>>
>>> Cheers,
>>> Thanet, AdWords API Team
>>>
>>> On Thursday, August 18, 2016 at 1:39:04 AM UTC+9, xtcsuk wrote:

 Hey Josh,

 Its me again, this time a different issue, was not sure to create a new 
 thread, so here it goes:

 The job:

 job id   account id
 344573194   1011654677

 has a "CANCELLED" status with a downloadUrl assigned to it, but on get 
 the results, it throws 404, may be another bug?

 regards,
 Zia

 On Wednesday, 17 August 2016 11:48:37 UTC+1, xtcsuk wrote:
>
> Hi Josh,
>
> Thank you for the clarification, on our side, however, as you can 
> imagine, we have logic to compare the two (upload/result) to marry up the 
> operation results.  So, if the numbers do not match, it just simply don't 
> work.
> Firstly, hoping for this not happen again (permanent fix), will keep 
> an eye and if so will come back to you.
>
> regards,
> Zia
>
> On Tuesday, 16 August 2016 19:06:50 UTC+1, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Zia,
>>
>> The count mismatch is an artifact of the failed download URL 
>> generation. You can safely ignore the mismatch (in this particular case) 
>> when processing the results from the URL.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, August 15, 2016 at 11:39:45 AM UTC-4, Josh Radcliff 
>> (AdWords API Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> I'm looking into that one and will get back to you with an update.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, August 15, 2016 at 9:08:56 AM UTC-4, xtcsuk wrote:

 Hi Josh,

 Thanks again, sorry my mistake.  

 On this subject, this is a job details where we have a discrepancy 
 in between the number of operations uploaded and number of operations 
 executed:

 job idaccount id
 342115475 7653799969

 our application is limited to assign maximum 3 number of 
 operations per job, so this job in our end has 3 operations, 
 however 
 the api results look different containing 5 number of operations.

 Appreciating the verification on this one, please.

 regards,
 Zia

 On Monday, 15 August 2016 13:39:21 UTC+1, Josh Radcliff (AdWords 
 API Team) wrote:
>
> Hi Zia,
>
> The job I was referring to was batch job ID 341175452, which had 
> status of CANCELED (please see your first email on this post). The 
> current 
> status remains as CANCELED.
>
> 
>   341175452
>   CANCELED
>   
> 2
> 2
> 66
> 0
>   
>   
> https://batch-job-download-prod...
> 20160911 170333 Etc/GMT
>   
> 
>
> Were you perhaps confusing this job with another one that Mike was 
> looking into for you?
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, August 15, 2016 at 7:10:33 AM UTC-4, xtcsuk wrote:
>>
>> Hi Josh,
>>
>> Thank you for your reply,
>>
>> The job in question did originally included a downloadUrl, 
>> however the progressStats is not somewhat correct. 
>> My question is around this, why the 
>> job's progressStats.estimatedPercentExecuted is at 60% and 

Re: api version 201605 - batchjobservice

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Zia,

I just asked for an update on that job. I'll reply back here as soon as I 
have more information.

Thanks,
Josh, AdWords API Team

On Tuesday, August 23, 2016 at 6:32:11 AM UTC-4, xtcsuk wrote:
>
> Hi Thanet,
>
> Any luck with this issue, as instructed, posted the requested info a few 
> days ago, hope you have got it.
>
> regards,
> Zia
>
> On Thursday, 18 August 2016 03:59:53 UTC+1, Thanet Knack Praneenararat 
> (AdWords API Team) wrote:
>>
>> Hello Zia,
>>
>> I'll handle this case instead of Josh.
>> It's fine to post in this thread again, but would be more easy for you to 
>> track the answers if you create another thread instead.
>>
>> For this case, could you please pass me your download URL as well using 
>> *Reply 
>> privately to author*?
>> I saw some of the results partially executed already, so there might be a 
>> problem of download URL.
>>
>> Cheers,
>> Thanet, AdWords API Team
>>
>> On Thursday, August 18, 2016 at 1:39:04 AM UTC+9, xtcsuk wrote:
>>>
>>> Hey Josh,
>>>
>>> Its me again, this time a different issue, was not sure to create a new 
>>> thread, so here it goes:
>>>
>>> The job:
>>>
>>> job id   account id
>>> 344573194   1011654677
>>>
>>> has a "CANCELLED" status with a downloadUrl assigned to it, but on get 
>>> the results, it throws 404, may be another bug?
>>>
>>> regards,
>>> Zia
>>>
>>> On Wednesday, 17 August 2016 11:48:37 UTC+1, xtcsuk wrote:

 Hi Josh,

 Thank you for the clarification, on our side, however, as you can 
 imagine, we have logic to compare the two (upload/result) to marry up the 
 operation results.  So, if the numbers do not match, it just simply don't 
 work.
 Firstly, hoping for this not happen again (permanent fix), will keep an 
 eye and if so will come back to you.

 regards,
 Zia

 On Tuesday, 16 August 2016 19:06:50 UTC+1, Josh Radcliff (AdWords API 
 Team) wrote:
>
> Hi Zia,
>
> The count mismatch is an artifact of the failed download URL 
> generation. You can safely ignore the mismatch (in this particular case) 
> when processing the results from the URL.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, August 15, 2016 at 11:39:45 AM UTC-4, Josh Radcliff 
> (AdWords API Team) wrote:
>>
>> Hi Zia,
>>
>> I'm looking into that one and will get back to you with an update.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, August 15, 2016 at 9:08:56 AM UTC-4, xtcsuk wrote:
>>>
>>> Hi Josh,
>>>
>>> Thanks again, sorry my mistake.  
>>>
>>> On this subject, this is a job details where we have a discrepancy 
>>> in between the number of operations uploaded and number of operations 
>>> executed:
>>>
>>> job idaccount id
>>> 342115475 7653799969
>>>
>>> our application is limited to assign maximum 3 number of 
>>> operations per job, so this job in our end has 3 operations, 
>>> however 
>>> the api results look different containing 5 number of operations.
>>>
>>> Appreciating the verification on this one, please.
>>>
>>> regards,
>>> Zia
>>>
>>> On Monday, 15 August 2016 13:39:21 UTC+1, Josh Radcliff (AdWords API 
>>> Team) wrote:

 Hi Zia,

 The job I was referring to was batch job ID 341175452, which had 
 status of CANCELED (please see your first email on this post). The 
 current 
 status remains as CANCELED.

 
   341175452
   CANCELED
   
 2
 2
 66
 0
   
   
 https://batch-job-download-prod...
 20160911 170333 Etc/GMT
   
 

 Were you perhaps confusing this job with another one that Mike was 
 looking into for you?

 Thanks,
 Josh, AdWords API Team

 On Monday, August 15, 2016 at 7:10:33 AM UTC-4, xtcsuk wrote:
>
> Hi Josh,
>
> Thank you for your reply,
>
> The job in question did originally included a downloadUrl, however 
> the progressStats is not somewhat correct. 
> My question is around this, why the 
> job's progressStats.estimatedPercentExecuted is at 60% and yet 
> BatchJobStatus is Done, I would expect estimatedPercentExecuted to be 
> 100% 
> for a "Done" job.  And not only that our records show 30k operations, 
> estimatedPercentExecuted is at 20k, hope this is clear, and apologies 
> if it 
> wasn't in the first post.
>
> regards,
> Zia
>
> On Friday, 12 August 2016 18:54:57 UTC+1, Josh Radcliff 

Re: api version 201605 - batchjobservice

[xtcsuk]

Hi Thanet,

Any luck with this issue, as instructed, posted the requested info a few 
days ago, hope you have got it.

regards,
Zia

On Thursday, 18 August 2016 03:59:53 UTC+1, Thanet Knack Praneenararat 
(AdWords API Team) wrote:
>
> Hello Zia,
>
> I'll handle this case instead of Josh.
> It's fine to post in this thread again, but would be more easy for you to 
> track the answers if you create another thread instead.
>
> For this case, could you please pass me your download URL as well using 
> *Reply 
> privately to author*?
> I saw some of the results partially executed already, so there might be a 
> problem of download URL.
>
> Cheers,
> Thanet, AdWords API Team
>
> On Thursday, August 18, 2016 at 1:39:04 AM UTC+9, xtcsuk wrote:
>>
>> Hey Josh,
>>
>> Its me again, this time a different issue, was not sure to create a new 
>> thread, so here it goes:
>>
>> The job:
>>
>> job id   account id
>> 344573194   1011654677
>>
>> has a "CANCELLED" status with a downloadUrl assigned to it, but on get 
>> the results, it throws 404, may be another bug?
>>
>> regards,
>> Zia
>>
>> On Wednesday, 17 August 2016 11:48:37 UTC+1, xtcsuk wrote:
>>>
>>> Hi Josh,
>>>
>>> Thank you for the clarification, on our side, however, as you can 
>>> imagine, we have logic to compare the two (upload/result) to marry up the 
>>> operation results.  So, if the numbers do not match, it just simply don't 
>>> work.
>>> Firstly, hoping for this not happen again (permanent fix), will keep an 
>>> eye and if so will come back to you.
>>>
>>> regards,
>>> Zia
>>>
>>> On Tuesday, 16 August 2016 19:06:50 UTC+1, Josh Radcliff (AdWords API 
>>> Team) wrote:

 Hi Zia,

 The count mismatch is an artifact of the failed download URL 
 generation. You can safely ignore the mismatch (in this particular case) 
 when processing the results from the URL.

 Thanks,
 Josh, AdWords API Team

 On Monday, August 15, 2016 at 11:39:45 AM UTC-4, Josh Radcliff (AdWords 
 API Team) wrote:
>
> Hi Zia,
>
> I'm looking into that one and will get back to you with an update.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, August 15, 2016 at 9:08:56 AM UTC-4, xtcsuk wrote:
>>
>> Hi Josh,
>>
>> Thanks again, sorry my mistake.  
>>
>> On this subject, this is a job details where we have a discrepancy in 
>> between the number of operations uploaded and number of operations 
>> executed:
>>
>> job idaccount id
>> 342115475 7653799969
>>
>> our application is limited to assign maximum 3 number of 
>> operations per job, so this job in our end has 3 operations, however 
>> the api results look different containing 5 number of operations.
>>
>> Appreciating the verification on this one, please.
>>
>> regards,
>> Zia
>>
>> On Monday, 15 August 2016 13:39:21 UTC+1, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> The job I was referring to was batch job ID 341175452, which had 
>>> status of CANCELED (please see your first email on this post). The 
>>> current 
>>> status remains as CANCELED.
>>>
>>> 
>>>   341175452
>>>   CANCELED
>>>   
>>> 2
>>> 2
>>> 66
>>> 0
>>>   
>>>   
>>> https://batch-job-download-prod...
>>> 20160911 170333 Etc/GMT
>>>   
>>> 
>>>
>>> Were you perhaps confusing this job with another one that Mike was 
>>> looking into for you?
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, August 15, 2016 at 7:10:33 AM UTC-4, xtcsuk wrote:

 Hi Josh,

 Thank you for your reply,

 The job in question did originally included a downloadUrl, however 
 the progressStats is not somewhat correct. 
 My question is around this, why the 
 job's progressStats.estimatedPercentExecuted is at 60% and yet 
 BatchJobStatus is Done, I would expect estimatedPercentExecuted to be 
 100% 
 for a "Done" job.  And not only that our records show 30k operations, 
 estimatedPercentExecuted is at 20k, hope this is clear, and apologies 
 if it 
 wasn't in the first post.

 regards,
 Zia

 On Friday, 12 August 2016 18:54:57 UTC+1, Josh Radcliff (AdWords 
 API Team) wrote:
>
> Hi Zia,
>
> A fix was applied for that job. If you retrieve the BatchJob 
> 
>  again, 
> you should get back a *downloadUrl* and be able to get the 
> results.
>

Re: api version 201605 - batchjobservice

['Thanet Knack Praneenararat (AdWords API Team)' via AdWords API Forum]

Hello Zia,

I'll handle this case instead of Josh.
It's fine to post in this thread again, but would be more easy for you to 
track the answers if you create another thread instead.

For this case, could you please pass me your download URL as well using *Reply 
privately to author*?
I saw some of the results partially executed already, so there might be a 
problem of download URL.

Cheers,
Thanet, AdWords API Team

On Thursday, August 18, 2016 at 1:39:04 AM UTC+9, xtcsuk wrote:
>
> Hey Josh,
>
> Its me again, this time a different issue, was not sure to create a new 
> thread, so here it goes:
>
> The job:
>
> job id   account id
> 344573194   1011654677
>
> has a "CANCELLED" status with a downloadUrl assigned to it, but on get the 
> results, it throws 404, may be another bug?
>
> regards,
> Zia
>
> On Wednesday, 17 August 2016 11:48:37 UTC+1, xtcsuk wrote:
>>
>> Hi Josh,
>>
>> Thank you for the clarification, on our side, however, as you can 
>> imagine, we have logic to compare the two (upload/result) to marry up the 
>> operation results.  So, if the numbers do not match, it just simply don't 
>> work.
>> Firstly, hoping for this not happen again (permanent fix), will keep an 
>> eye and if so will come back to you.
>>
>> regards,
>> Zia
>>
>> On Tuesday, 16 August 2016 19:06:50 UTC+1, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> The count mismatch is an artifact of the failed download URL generation. 
>>> You can safely ignore the mismatch (in this particular case) when 
>>> processing the results from the URL.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, August 15, 2016 at 11:39:45 AM UTC-4, Josh Radcliff (AdWords 
>>> API Team) wrote:

 Hi Zia,

 I'm looking into that one and will get back to you with an update.

 Thanks,
 Josh, AdWords API Team

 On Monday, August 15, 2016 at 9:08:56 AM UTC-4, xtcsuk wrote:
>
> Hi Josh,
>
> Thanks again, sorry my mistake.  
>
> On this subject, this is a job details where we have a discrepancy in 
> between the number of operations uploaded and number of operations 
> executed:
>
> job idaccount id
> 342115475 7653799969
>
> our application is limited to assign maximum 3 number of 
> operations per job, so this job in our end has 3 operations, however 
> the api results look different containing 5 number of operations.
>
> Appreciating the verification on this one, please.
>
> regards,
> Zia
>
> On Monday, 15 August 2016 13:39:21 UTC+1, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Zia,
>>
>> The job I was referring to was batch job ID 341175452, which had 
>> status of CANCELED (please see your first email on this post). The 
>> current 
>> status remains as CANCELED.
>>
>> 
>>   341175452
>>   CANCELED
>>   
>> 2
>> 2
>> 66
>> 0
>>   
>>   
>> https://batch-job-download-prod...
>> 20160911 170333 Etc/GMT
>>   
>> 
>>
>> Were you perhaps confusing this job with another one that Mike was 
>> looking into for you?
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, August 15, 2016 at 7:10:33 AM UTC-4, xtcsuk wrote:
>>>
>>> Hi Josh,
>>>
>>> Thank you for your reply,
>>>
>>> The job in question did originally included a downloadUrl, however 
>>> the progressStats is not somewhat correct. 
>>> My question is around this, why the 
>>> job's progressStats.estimatedPercentExecuted is at 60% and yet 
>>> BatchJobStatus is Done, I would expect estimatedPercentExecuted to be 
>>> 100% 
>>> for a "Done" job.  And not only that our records show 30k operations, 
>>> estimatedPercentExecuted is at 20k, hope this is clear, and apologies 
>>> if it 
>>> wasn't in the first post.
>>>
>>> regards,
>>> Zia
>>>
>>> On Friday, 12 August 2016 18:54:57 UTC+1, Josh Radcliff (AdWords API 
>>> Team) wrote:

 Hi Zia,

 A fix was applied for that job. If you retrieve the BatchJob 
 
  again, 
 you should get back a *downloadUrl* and be able to get the results.

 Thanks,
 Josh, AdWords API Team

 On Friday, August 12, 2016 at 10:55:00 AM UTC-4, Josh Radcliff 
 (AdWords API Team) wrote:
>
> Hi Zia,
>
> Mike just pointed out that this is a different issue from the 
> other post. I'm following up on this one and will get back to you as 
> soon 
> as I have more information.

Re: api version 201605 - batchjobservice

[xtcsuk]

Hey Josh,

Its me again, this time a different issue, was not sure to create a new 
thread, so here it goes:

The job:

job id   account id
344573194   1011654677

has a "CANCELLED" status with a downloadUrl assigned to it, but on get the 
results, it throws 404, may be another bug?

regards,
Zia

On Wednesday, 17 August 2016 11:48:37 UTC+1, xtcsuk wrote:
>
> Hi Josh,
>
> Thank you for the clarification, on our side, however, as you can imagine, 
> we have logic to compare the two (upload/result) to marry up the operation 
> results.  So, if the numbers do not match, it just simply don't work.
> Firstly, hoping for this not happen again (permanent fix), will keep an 
> eye and if so will come back to you.
>
> regards,
> Zia
>
> On Tuesday, 16 August 2016 19:06:50 UTC+1, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Zia,
>>
>> The count mismatch is an artifact of the failed download URL generation. 
>> You can safely ignore the mismatch (in this particular case) when 
>> processing the results from the URL.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, August 15, 2016 at 11:39:45 AM UTC-4, Josh Radcliff (AdWords 
>> API Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> I'm looking into that one and will get back to you with an update.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, August 15, 2016 at 9:08:56 AM UTC-4, xtcsuk wrote:

 Hi Josh,

 Thanks again, sorry my mistake.  

 On this subject, this is a job details where we have a discrepancy in 
 between the number of operations uploaded and number of operations 
 executed:

 job idaccount id
 342115475 7653799969

 our application is limited to assign maximum 3 number of operations 
 per job, so this job in our end has 3 operations, however the api 
 results look different containing 5 number of operations.

 Appreciating the verification on this one, please.

 regards,
 Zia

 On Monday, 15 August 2016 13:39:21 UTC+1, Josh Radcliff (AdWords API 
 Team) wrote:
>
> Hi Zia,
>
> The job I was referring to was batch job ID 341175452, which had 
> status of CANCELED (please see your first email on this post). The 
> current 
> status remains as CANCELED.
>
> 
>   341175452
>   CANCELED
>   
> 2
> 2
> 66
> 0
>   
>   
> https://batch-job-download-prod...
> 20160911 170333 Etc/GMT
>   
> 
>
> Were you perhaps confusing this job with another one that Mike was 
> looking into for you?
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, August 15, 2016 at 7:10:33 AM UTC-4, xtcsuk wrote:
>>
>> Hi Josh,
>>
>> Thank you for your reply,
>>
>> The job in question did originally included a downloadUrl, however 
>> the progressStats is not somewhat correct. 
>> My question is around this, why the 
>> job's progressStats.estimatedPercentExecuted is at 60% and yet 
>> BatchJobStatus is Done, I would expect estimatedPercentExecuted to be 
>> 100% 
>> for a "Done" job.  And not only that our records show 30k operations, 
>> estimatedPercentExecuted is at 20k, hope this is clear, and apologies if 
>> it 
>> wasn't in the first post.
>>
>> regards,
>> Zia
>>
>> On Friday, 12 August 2016 18:54:57 UTC+1, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> A fix was applied for that job. If you retrieve the BatchJob 
>>> 
>>>  again, 
>>> you should get back a *downloadUrl* and be able to get the results.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Friday, August 12, 2016 at 10:55:00 AM UTC-4, Josh Radcliff 
>>> (AdWords API Team) wrote:

 Hi Zia,

 Mike just pointed out that this is a different issue from the other 
 post. I'm following up on this one and will get back to you as soon as 
 I 
 have more information.

 Thanks,
 Josh, AdWords API Team

 On Thursday, August 11, 2016 at 2:04:14 PM UTC-4, Josh Radcliff 
 (AdWords API Team) wrote:
>
> Hi Zia,
>
> I see you already are discussing this issue with Mike on another 
> post 
> ,
>  
> so I'll mark this one a duplicate. Mike is still looking into this 
> issue 
> for you and will respond on the other post.
>
> Thanks,
> Josh, AdWords API Team
>
> On Thursday, August 11, 

Re: api version 201605 - batchjobservice

[xtcsuk]

Hi Josh,

Thank you for the clarification, on our side, however, as you can imagine, 
we have logic to compare the two (upload/result) to marry up the operation 
results.  So, if the numbers do not match, it just simply don't work.
Firstly, hoping for this not happen again (permanent fix), will keep an eye 
and if so will come back to you.

regards,
Zia

On Tuesday, 16 August 2016 19:06:50 UTC+1, Josh Radcliff (AdWords API Team) 
wrote:
>
> Hi Zia,
>
> The count mismatch is an artifact of the failed download URL generation. 
> You can safely ignore the mismatch (in this particular case) when 
> processing the results from the URL.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, August 15, 2016 at 11:39:45 AM UTC-4, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Zia,
>>
>> I'm looking into that one and will get back to you with an update.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, August 15, 2016 at 9:08:56 AM UTC-4, xtcsuk wrote:
>>>
>>> Hi Josh,
>>>
>>> Thanks again, sorry my mistake.  
>>>
>>> On this subject, this is a job details where we have a discrepancy in 
>>> between the number of operations uploaded and number of operations executed:
>>>
>>> job idaccount id
>>> 342115475 7653799969
>>>
>>> our application is limited to assign maximum 3 number of operations 
>>> per job, so this job in our end has 3 operations, however the api 
>>> results look different containing 5 number of operations.
>>>
>>> Appreciating the verification on this one, please.
>>>
>>> regards,
>>> Zia
>>>
>>> On Monday, 15 August 2016 13:39:21 UTC+1, Josh Radcliff (AdWords API 
>>> Team) wrote:

 Hi Zia,

 The job I was referring to was batch job ID 341175452, which had status 
 of CANCELED (please see your first email on this post). The current status 
 remains as CANCELED.

 
   341175452
   CANCELED
   
 2
 2
 66
 0
   
   
 https://batch-job-download-prod...
 20160911 170333 Etc/GMT
   
 

 Were you perhaps confusing this job with another one that Mike was 
 looking into for you?

 Thanks,
 Josh, AdWords API Team

 On Monday, August 15, 2016 at 7:10:33 AM UTC-4, xtcsuk wrote:
>
> Hi Josh,
>
> Thank you for your reply,
>
> The job in question did originally included a downloadUrl, however the 
> progressStats is not somewhat correct. 
> My question is around this, why the 
> job's progressStats.estimatedPercentExecuted is at 60% and yet 
> BatchJobStatus is Done, I would expect estimatedPercentExecuted to be 
> 100% 
> for a "Done" job.  And not only that our records show 30k operations, 
> estimatedPercentExecuted is at 20k, hope this is clear, and apologies if 
> it 
> wasn't in the first post.
>
> regards,
> Zia
>
> On Friday, 12 August 2016 18:54:57 UTC+1, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Zia,
>>
>> A fix was applied for that job. If you retrieve the BatchJob 
>> 
>>  again, 
>> you should get back a *downloadUrl* and be able to get the results.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Friday, August 12, 2016 at 10:55:00 AM UTC-4, Josh Radcliff 
>> (AdWords API Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> Mike just pointed out that this is a different issue from the other 
>>> post. I'm following up on this one and will get back to you as soon as 
>>> I 
>>> have more information.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Thursday, August 11, 2016 at 2:04:14 PM UTC-4, Josh Radcliff 
>>> (AdWords API Team) wrote:

 Hi Zia,

 I see you already are discussing this issue with Mike on another 
 post 
 ,
  
 so I'll mark this one a duplicate. Mike is still looking into this 
 issue 
 for you and will respond on the other post.

 Thanks,
 Josh, AdWords API Team

 On Thursday, August 11, 2016 at 10:51:28 AM UTC-4, xtcsuk wrote:
>
> Hello,
>
> A question around a cancelled job, on getting result for a job, 
> the data tells us the job has been cancelled, no downloadUrl and with 
> the 
> following stats:
>
> service call:
> batchjobservice.get(selector).entries
>
> api call result:
> estimatedPercentExecuted: 60%, numOperationsExecuted: 2, 
> numOperationsSucceeded: 2, numResultsWritten: 0
>
> our 

Re: api version 201605 - batchjobservice

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Zia,

The count mismatch is an artifact of the failed download URL generation. 
You can safely ignore the mismatch (in this particular case) when 
processing the results from the URL.

Thanks,
Josh, AdWords API Team

On Monday, August 15, 2016 at 11:39:45 AM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Zia,
>
> I'm looking into that one and will get back to you with an update.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, August 15, 2016 at 9:08:56 AM UTC-4, xtcsuk wrote:
>>
>> Hi Josh,
>>
>> Thanks again, sorry my mistake.  
>>
>> On this subject, this is a job details where we have a discrepancy in 
>> between the number of operations uploaded and number of operations executed:
>>
>> job idaccount id
>> 342115475 7653799969
>>
>> our application is limited to assign maximum 3 number of operations 
>> per job, so this job in our end has 3 operations, however the api 
>> results look different containing 5 number of operations.
>>
>> Appreciating the verification on this one, please.
>>
>> regards,
>> Zia
>>
>> On Monday, 15 August 2016 13:39:21 UTC+1, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> The job I was referring to was batch job ID 341175452, which had status 
>>> of CANCELED (please see your first email on this post). The current status 
>>> remains as CANCELED.
>>>
>>> 
>>>   341175452
>>>   CANCELED
>>>   
>>> 2
>>> 2
>>> 66
>>> 0
>>>   
>>>   
>>> https://batch-job-download-prod...
>>> 20160911 170333 Etc/GMT
>>>   
>>> 
>>>
>>> Were you perhaps confusing this job with another one that Mike was 
>>> looking into for you?
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, August 15, 2016 at 7:10:33 AM UTC-4, xtcsuk wrote:

 Hi Josh,

 Thank you for your reply,

 The job in question did originally included a downloadUrl, however the 
 progressStats is not somewhat correct. 
 My question is around this, why the 
 job's progressStats.estimatedPercentExecuted is at 60% and yet 
 BatchJobStatus is Done, I would expect estimatedPercentExecuted to be 100% 
 for a "Done" job.  And not only that our records show 30k operations, 
 estimatedPercentExecuted is at 20k, hope this is clear, and apologies if 
 it 
 wasn't in the first post.

 regards,
 Zia

 On Friday, 12 August 2016 18:54:57 UTC+1, Josh Radcliff (AdWords API 
 Team) wrote:
>
> Hi Zia,
>
> A fix was applied for that job. If you retrieve the BatchJob 
> 
>  again, 
> you should get back a *downloadUrl* and be able to get the results.
>
> Thanks,
> Josh, AdWords API Team
>
> On Friday, August 12, 2016 at 10:55:00 AM UTC-4, Josh Radcliff 
> (AdWords API Team) wrote:
>>
>> Hi Zia,
>>
>> Mike just pointed out that this is a different issue from the other 
>> post. I'm following up on this one and will get back to you as soon as I 
>> have more information.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, August 11, 2016 at 2:04:14 PM UTC-4, Josh Radcliff 
>> (AdWords API Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> I see you already are discussing this issue with Mike on another 
>>> post 
>>> , 
>>> so I'll mark this one a duplicate. Mike is still looking into this 
>>> issue 
>>> for you and will respond on the other post.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Thursday, August 11, 2016 at 10:51:28 AM UTC-4, xtcsuk wrote:

 Hello,

 A question around a cancelled job, on getting result for a job, the 
 data tells us the job has been cancelled, no downloadUrl and with the 
 following stats:

 service call:
 batchjobservice.get(selector).entries

 api call result:
 estimatedPercentExecuted: 60%, numOperationsExecuted: 2, 
 numOperationsSucceeded: 2, numResultsWritten: 0

 our record shows, 3 operations are attached to this job.

 The jobid = 341175452, and accountid = 8227096083

 Based on this, how would then we update our end of the bargain, 
 with no downloadUrl, we can't do anything really, and surely that 
 leaves us 
 in unknown status.


 regards,
 Zia

>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts

Re: api version 201605

['Michael Cloonan (AdWords API Team)' via AdWords API Forum]

Hello,

There will be no notification when the server side fix is applied to 
prevent this from happening again. I would make sure to include code to 
check for this case and log the batch job ID just in case. I apologize for 
the inconvenience.

Regards,
Mike, AdWords API Team

On Monday, August 15, 2016 at 12:36:48 PM UTC-4, xtcsuk wrote:
>
> Thanks Mike,
>
> Appreciating the feedback, as for the actual fix (patch to fix the api 
> side), do we get notified, or should we just keep on looking out for this 
> symptom?
>
> regards,
> Zia
>
> On Friday, 12 August 2016 18:14:56 UTC+1, Michael Cloonan (AdWords API 
> Team) wrote:
>>
>> Hello,
>>
>> As for the two job IDs you provided for this thread, engineering has just 
>> regenerated the download URLs, so you should be able to access the results 
>> now.
>>
>> Regards,
>> Mike, AdWords API Team
>>
>> On Friday, August 12, 2016 at 8:32:02 AM UTC-4, Michael Cloonan (AdWords 
>> API Team) wrote:
>>>
>>> Hello,
>>>
>>> I apologize for that; it was simply a misunderstanding.
>>>
>>> I have reopened the other thread for us to track that issue separately, 
>>> and we will be responding there once we've had a chance to look into it.
>>>
>>> Regards,
>>> Mike, AdWords API Team
>>>
>>> On Friday, August 12, 2016 at 5:42:25 AM UTC-4, xtcsuk wrote:

 Thank you Mike,

 I posted another issue on the 11th of August titled "api version 201605 
 - batchjobservice", but is marked as duplicate.  Can't open the thread 
 anymore, its taking me here:
 This is a different issue, we have downloadUrl, Done as job status, but 
 the stats does not reflect the total number of operations, not sure why 
 marked as duplicate, can provide the details again if needed.

 regards,
 Zia

 On Thursday, 11 August 2016 14:25:14 UTC+1, Michael Cloonan (AdWords 
 API Team) wrote:
>
> Hello,
>
> I will pass these IDs along to engineering so they can get the 
> download URL to show properly.
>
> Regards,
> Mike, AdWords API Team
>
> On Thursday, August 11, 2016 at 8:10:54 AM UTC-4, xtcsuk wrote:
>>
>> Hi Mike,
>>
>> Thanks for the clarification, looks like the empty download url bug 
>> still persists, for a handful number of jobs, at least.  Here is the 
>> list 
>> (been identified so far)
>>
>> JobId,   AccountId   Approximate 
>> upload time
>> 34100429769850537022016-08-11 
>> 10:42:34.140
>> 34065384486905392772016-08-11 
>> 00:18:36.320
>>
>> regards,
>> Zia
>>
>> On Tuesday, 9 August 2016 19:04:36 UTC+1, Michael Cloonan (AdWords 
>> API Team) wrote:
>>>
>>> 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 

Re: api version 201605

[xtcsuk]

Thanks Mike,

Appreciating the feedback, as for the actual fix (patch to fix the api 
side), do we get notified, or should we just keep on looking out for this 
symptom?

regards,
Zia

On Friday, 12 August 2016 18:14:56 UTC+1, Michael Cloonan (AdWords API 
Team) wrote:
>
> Hello,
>
> As for the two job IDs you provided for this thread, engineering has just 
> regenerated the download URLs, so you should be able to access the results 
> now.
>
> Regards,
> Mike, AdWords API Team
>
> On Friday, August 12, 2016 at 8:32:02 AM UTC-4, Michael Cloonan (AdWords 
> API Team) wrote:
>>
>> Hello,
>>
>> I apologize for that; it was simply a misunderstanding.
>>
>> I have reopened the other thread for us to track that issue separately, 
>> and we will be responding there once we've had a chance to look into it.
>>
>> Regards,
>> Mike, AdWords API Team
>>
>> On Friday, August 12, 2016 at 5:42:25 AM UTC-4, xtcsuk wrote:
>>>
>>> Thank you Mike,
>>>
>>> I posted another issue on the 11th of August titled "api version 201605 
>>> - batchjobservice", but is marked as duplicate.  Can't open the thread 
>>> anymore, its taking me here:
>>> This is a different issue, we have downloadUrl, Done as job status, but 
>>> the stats does not reflect the total number of operations, not sure why 
>>> marked as duplicate, can provide the details again if needed.
>>>
>>> regards,
>>> Zia
>>>
>>> On Thursday, 11 August 2016 14:25:14 UTC+1, Michael Cloonan (AdWords API 
>>> Team) wrote:

 Hello,

 I will pass these IDs along to engineering so they can get the download 
 URL to show properly.

 Regards,
 Mike, AdWords API Team

 On Thursday, August 11, 2016 at 8:10:54 AM UTC-4, xtcsuk wrote:
>
> Hi Mike,
>
> Thanks for the clarification, looks like the empty download url bug 
> still persists, for a handful number of jobs, at least.  Here is the list 
> (been identified so far)
>
> JobId,   AccountId   Approximate 
> upload time
> 34100429769850537022016-08-11 
> 10:42:34.140
> 34065384486905392772016-08-11 
> 00:18:36.320
>
> regards,
> Zia
>
> On Tuesday, 9 August 2016 19:04:36 UTC+1, Michael Cloonan (AdWords API 
> Team) wrote:
>>
>> 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 

Re: api version 201605 - batchjobservice

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Zia,

I'm looking into that one and will get back to you with an update.

Thanks,
Josh, AdWords API Team

On Monday, August 15, 2016 at 9:08:56 AM UTC-4, xtcsuk wrote:
>
> Hi Josh,
>
> Thanks again, sorry my mistake.  
>
> On this subject, this is a job details where we have a discrepancy in 
> between the number of operations uploaded and number of operations executed:
>
> job idaccount id
> 342115475 7653799969
>
> our application is limited to assign maximum 3 number of operations 
> per job, so this job in our end has 3 operations, however the api 
> results look different containing 5 number of operations.
>
> Appreciating the verification on this one, please.
>
> regards,
> Zia
>
> On Monday, 15 August 2016 13:39:21 UTC+1, Josh Radcliff (AdWords API Team) 
> wrote:
>>
>> Hi Zia,
>>
>> The job I was referring to was batch job ID 341175452, which had status 
>> of CANCELED (please see your first email on this post). The current status 
>> remains as CANCELED.
>>
>> 
>>   341175452
>>   CANCELED
>>   
>> 2
>> 2
>> 66
>> 0
>>   
>>   
>> https://batch-job-download-prod...
>> 20160911 170333 Etc/GMT
>>   
>> 
>>
>> Were you perhaps confusing this job with another one that Mike was 
>> looking into for you?
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, August 15, 2016 at 7:10:33 AM UTC-4, xtcsuk wrote:
>>>
>>> Hi Josh,
>>>
>>> Thank you for your reply,
>>>
>>> The job in question did originally included a downloadUrl, however the 
>>> progressStats is not somewhat correct. 
>>> My question is around this, why the 
>>> job's progressStats.estimatedPercentExecuted is at 60% and yet 
>>> BatchJobStatus is Done, I would expect estimatedPercentExecuted to be 100% 
>>> for a "Done" job.  And not only that our records show 30k operations, 
>>> estimatedPercentExecuted is at 20k, hope this is clear, and apologies if it 
>>> wasn't in the first post.
>>>
>>> regards,
>>> Zia
>>>
>>> On Friday, 12 August 2016 18:54:57 UTC+1, Josh Radcliff (AdWords API 
>>> Team) wrote:

 Hi Zia,

 A fix was applied for that job. If you retrieve the BatchJob 
 
  again, 
 you should get back a *downloadUrl* and be able to get the results.

 Thanks,
 Josh, AdWords API Team

 On Friday, August 12, 2016 at 10:55:00 AM UTC-4, Josh Radcliff (AdWords 
 API Team) wrote:
>
> Hi Zia,
>
> Mike just pointed out that this is a different issue from the other 
> post. I'm following up on this one and will get back to you as soon as I 
> have more information.
>
> Thanks,
> Josh, AdWords API Team
>
> On Thursday, August 11, 2016 at 2:04:14 PM UTC-4, Josh Radcliff 
> (AdWords API Team) wrote:
>>
>> Hi Zia,
>>
>> I see you already are discussing this issue with Mike on another post 
>> , 
>> so I'll mark this one a duplicate. Mike is still looking into this issue 
>> for you and will respond on the other post.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, August 11, 2016 at 10:51:28 AM UTC-4, xtcsuk wrote:
>>>
>>> Hello,
>>>
>>> A question around a cancelled job, on getting result for a job, the 
>>> data tells us the job has been cancelled, no downloadUrl and with the 
>>> following stats:
>>>
>>> service call:
>>> batchjobservice.get(selector).entries
>>>
>>> api call result:
>>> estimatedPercentExecuted: 60%, numOperationsExecuted: 2, 
>>> numOperationsSucceeded: 2, numResultsWritten: 0
>>>
>>> our record shows, 3 operations are attached to this job.
>>>
>>> The jobid = 341175452, and accountid = 8227096083
>>>
>>> Based on this, how would then we update our end of the bargain, with 
>>> no downloadUrl, we can't do anything really, and surely that leaves us 
>>> in 
>>> unknown status.
>>>
>>>
>>> regards,
>>> Zia
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 

Re: api version 201605 - batchjobservice

[xtcsuk]

Hi Josh,

Thanks again, sorry my mistake.  

On this subject, this is a job details where we have a discrepancy in 
between the number of operations uploaded and number of operations executed:

job idaccount id
342115475 7653799969

our application is limited to assign maximum 3 number of operations per 
job, so this job in our end has 3 operations, however the api results 
look different containing 5 number of operations.

Appreciating the verification on this one, please.

regards,
Zia

On Monday, 15 August 2016 13:39:21 UTC+1, Josh Radcliff (AdWords API Team) 
wrote:
>
> Hi Zia,
>
> The job I was referring to was batch job ID 341175452, which had status of 
> CANCELED (please see your first email on this post). The current status 
> remains as CANCELED.
>
> 
>   341175452
>   CANCELED
>   
> 2
> 2
> 66
> 0
>   
>   
> https://batch-job-download-prod...
> 20160911 170333 Etc/GMT
>   
> 
>
> Were you perhaps confusing this job with another one that Mike was looking 
> into for you?
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, August 15, 2016 at 7:10:33 AM UTC-4, xtcsuk wrote:
>>
>> Hi Josh,
>>
>> Thank you for your reply,
>>
>> The job in question did originally included a downloadUrl, however the 
>> progressStats is not somewhat correct. 
>> My question is around this, why the 
>> job's progressStats.estimatedPercentExecuted is at 60% and yet 
>> BatchJobStatus is Done, I would expect estimatedPercentExecuted to be 100% 
>> for a "Done" job.  And not only that our records show 30k operations, 
>> estimatedPercentExecuted is at 20k, hope this is clear, and apologies if it 
>> wasn't in the first post.
>>
>> regards,
>> Zia
>>
>> On Friday, 12 August 2016 18:54:57 UTC+1, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> A fix was applied for that job. If you retrieve the BatchJob 
>>> 
>>>  again, 
>>> you should get back a *downloadUrl* and be able to get the results.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Friday, August 12, 2016 at 10:55:00 AM UTC-4, Josh Radcliff (AdWords 
>>> API Team) wrote:

 Hi Zia,

 Mike just pointed out that this is a different issue from the other 
 post. I'm following up on this one and will get back to you as soon as I 
 have more information.

 Thanks,
 Josh, AdWords API Team

 On Thursday, August 11, 2016 at 2:04:14 PM UTC-4, Josh Radcliff 
 (AdWords API Team) wrote:
>
> Hi Zia,
>
> I see you already are discussing this issue with Mike on another post 
> , 
> so I'll mark this one a duplicate. Mike is still looking into this issue 
> for you and will respond on the other post.
>
> Thanks,
> Josh, AdWords API Team
>
> On Thursday, August 11, 2016 at 10:51:28 AM UTC-4, xtcsuk wrote:
>>
>> Hello,
>>
>> A question around a cancelled job, on getting result for a job, the 
>> data tells us the job has been cancelled, no downloadUrl and with the 
>> following stats:
>>
>> service call:
>> batchjobservice.get(selector).entries
>>
>> api call result:
>> estimatedPercentExecuted: 60%, numOperationsExecuted: 2, 
>> numOperationsSucceeded: 2, numResultsWritten: 0
>>
>> our record shows, 3 operations are attached to this job.
>>
>> The jobid = 341175452, and accountid = 8227096083
>>
>> Based on this, how would then we update our end of the bargain, with 
>> no downloadUrl, we can't do anything really, and surely that leaves us 
>> in 
>> unknown status.
>>
>>
>> regards,
>> Zia
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/eed38dc7-74ea-4ad1-b7a4-7203256fcb78%40googlegroups.com.
For more options, 

Re: api version 201605 - batchjobservice

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Zia,

The job I was referring to was batch job ID 341175452, which had status of 
CANCELED (please see your first email on this post). The current status 
remains as CANCELED.


  341175452
  CANCELED
  
2
2
66
0
  
  
https://batch-job-download-prod...
20160911 170333 Etc/GMT
  


Were you perhaps confusing this job with another one that Mike was looking 
into for you?

Thanks,
Josh, AdWords API Team

On Monday, August 15, 2016 at 7:10:33 AM UTC-4, xtcsuk wrote:
>
> Hi Josh,
>
> Thank you for your reply,
>
> The job in question did originally included a downloadUrl, however the 
> progressStats is not somewhat correct. 
> My question is around this, why the 
> job's progressStats.estimatedPercentExecuted is at 60% and yet 
> BatchJobStatus is Done, I would expect estimatedPercentExecuted to be 100% 
> for a "Done" job.  And not only that our records show 30k operations, 
> estimatedPercentExecuted is at 20k, hope this is clear, and apologies if it 
> wasn't in the first post.
>
> regards,
> Zia
>
> On Friday, 12 August 2016 18:54:57 UTC+1, Josh Radcliff (AdWords API Team) 
> wrote:
>>
>> Hi Zia,
>>
>> A fix was applied for that job. If you retrieve the BatchJob 
>> 
>>  again, 
>> you should get back a *downloadUrl* and be able to get the results.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Friday, August 12, 2016 at 10:55:00 AM UTC-4, Josh Radcliff (AdWords 
>> API Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> Mike just pointed out that this is a different issue from the other 
>>> post. I'm following up on this one and will get back to you as soon as I 
>>> have more information.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Thursday, August 11, 2016 at 2:04:14 PM UTC-4, Josh Radcliff (AdWords 
>>> API Team) wrote:

 Hi Zia,

 I see you already are discussing this issue with Mike on another post 
 , 
 so I'll mark this one a duplicate. Mike is still looking into this issue 
 for you and will respond on the other post.

 Thanks,
 Josh, AdWords API Team

 On Thursday, August 11, 2016 at 10:51:28 AM UTC-4, xtcsuk wrote:
>
> Hello,
>
> A question around a cancelled job, on getting result for a job, the 
> data tells us the job has been cancelled, no downloadUrl and with the 
> following stats:
>
> service call:
> batchjobservice.get(selector).entries
>
> api call result:
> estimatedPercentExecuted: 60%, numOperationsExecuted: 2, 
> numOperationsSucceeded: 2, numResultsWritten: 0
>
> our record shows, 3 operations are attached to this job.
>
> The jobid = 341175452, and accountid = 8227096083
>
> Based on this, how would then we update our end of the bargain, with 
> no downloadUrl, we can't do anything really, and surely that leaves us in 
> unknown status.
>
>
> regards,
> Zia
>


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/5aa40b0e-4014-4b25-953f-73386a7dfa75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605 - batchjobservice

[xtcsuk]

Hi Josh,

Thank you for your reply,

The job in question did originally included a downloadUrl, however the 
progressStats is not somewhat correct. 
My question is around this, why the 
job's progressStats.estimatedPercentExecuted is at 60% and yet 
BatchJobStatus is Done, I would expect estimatedPercentExecuted to be 100% 
for a "Done" job.  And not only that our records show 30k operations, 
estimatedPercentExecuted is at 20k, hope this is clear, and apologies if it 
wasn't in the first post.

regards,
Zia

On Friday, 12 August 2016 18:54:57 UTC+1, Josh Radcliff (AdWords API Team) 
wrote:
>
> Hi Zia,
>
> A fix was applied for that job. If you retrieve the BatchJob 
> 
>  again, 
> you should get back a *downloadUrl* and be able to get the results.
>
> Thanks,
> Josh, AdWords API Team
>
> On Friday, August 12, 2016 at 10:55:00 AM UTC-4, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Zia,
>>
>> Mike just pointed out that this is a different issue from the other post. 
>> I'm following up on this one and will get back to you as soon as I have 
>> more information.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, August 11, 2016 at 2:04:14 PM UTC-4, Josh Radcliff (AdWords 
>> API Team) wrote:
>>>
>>> Hi Zia,
>>>
>>> I see you already are discussing this issue with Mike on another post 
>>> , 
>>> so I'll mark this one a duplicate. Mike is still looking into this issue 
>>> for you and will respond on the other post.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Thursday, August 11, 2016 at 10:51:28 AM UTC-4, xtcsuk wrote:

 Hello,

 A question around a cancelled job, on getting result for a job, the 
 data tells us the job has been cancelled, no downloadUrl and with the 
 following stats:

 service call:
 batchjobservice.get(selector).entries

 api call result:
 estimatedPercentExecuted: 60%, numOperationsExecuted: 2, 
 numOperationsSucceeded: 2, numResultsWritten: 0

 our record shows, 3 operations are attached to this job.

 The jobid = 341175452, and accountid = 8227096083

 Based on this, how would then we update our end of the bargain, with no 
 downloadUrl, we can't do anything really, and surely that leaves us in 
 unknown status.


 regards,
 Zia

>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/f734c973-ca99-4315-9658-f3d23123f755%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605 - batchjobservice

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Zia,

A fix was applied for that job. If you retrieve the BatchJob 

 again, 
you should get back a *downloadUrl* and be able to get the results.

Thanks,
Josh, AdWords API Team

On Friday, August 12, 2016 at 10:55:00 AM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Zia,
>
> Mike just pointed out that this is a different issue from the other post. 
> I'm following up on this one and will get back to you as soon as I have 
> more information.
>
> Thanks,
> Josh, AdWords API Team
>
> On Thursday, August 11, 2016 at 2:04:14 PM UTC-4, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Zia,
>>
>> I see you already are discussing this issue with Mike on another post 
>> , 
>> so I'll mark this one a duplicate. Mike is still looking into this issue 
>> for you and will respond on the other post.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, August 11, 2016 at 10:51:28 AM UTC-4, xtcsuk wrote:
>>>
>>> Hello,
>>>
>>> A question around a cancelled job, on getting result for a job, the data 
>>> tells us the job has been cancelled, no downloadUrl and with the following 
>>> stats:
>>>
>>> service call:
>>> batchjobservice.get(selector).entries
>>>
>>> api call result:
>>> estimatedPercentExecuted: 60%, numOperationsExecuted: 2, 
>>> numOperationsSucceeded: 2, numResultsWritten: 0
>>>
>>> our record shows, 3 operations are attached to this job.
>>>
>>> The jobid = 341175452, and accountid = 8227096083
>>>
>>> Based on this, how would then we update our end of the bargain, with no 
>>> downloadUrl, we can't do anything really, and surely that leaves us in 
>>> unknown status.
>>>
>>>
>>> regards,
>>> Zia
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/d73d16af-214a-420d-8960-af4312c4e7e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605

['Michael Cloonan (AdWords API Team)' via AdWords API Forum]

Hello,

As for the two job IDs you provided for this thread, engineering has just 
regenerated the download URLs, so you should be able to access the results 
now.

Regards,
Mike, AdWords API Team

On Friday, August 12, 2016 at 8:32:02 AM UTC-4, Michael Cloonan (AdWords 
API Team) wrote:
>
> Hello,
>
> I apologize for that; it was simply a misunderstanding.
>
> I have reopened the other thread for us to track that issue separately, 
> and we will be responding there once we've had a chance to look into it.
>
> Regards,
> Mike, AdWords API Team
>
> On Friday, August 12, 2016 at 5:42:25 AM UTC-4, xtcsuk wrote:
>>
>> Thank you Mike,
>>
>> I posted another issue on the 11th of August titled "api version 201605 - 
>> batchjobservice", but is marked as duplicate.  Can't open the thread 
>> anymore, its taking me here:
>> This is a different issue, we have downloadUrl, Done as job status, but 
>> the stats does not reflect the total number of operations, not sure why 
>> marked as duplicate, can provide the details again if needed.
>>
>> regards,
>> Zia
>>
>> On Thursday, 11 August 2016 14:25:14 UTC+1, Michael Cloonan (AdWords API 
>> Team) wrote:
>>>
>>> Hello,
>>>
>>> I will pass these IDs along to engineering so they can get the download 
>>> URL to show properly.
>>>
>>> Regards,
>>> Mike, AdWords API Team
>>>
>>> On Thursday, August 11, 2016 at 8:10:54 AM UTC-4, xtcsuk wrote:

 Hi Mike,

 Thanks for the clarification, looks like the empty download url bug 
 still persists, for a handful number of jobs, at least.  Here is the list 
 (been identified so far)

 JobId,   AccountId   Approximate 
 upload time
 34100429769850537022016-08-11 
 10:42:34.140
 34065384486905392772016-08-11 
 00:18:36.320

 regards,
 Zia

 On Tuesday, 9 August 2016 19:04:36 UTC+1, Michael Cloonan (AdWords API 
 Team) wrote:
>
> 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. 

Re: api version 201605 - batchjobservice

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Zia,

Mike just pointed out that this is a different issue from the other post. 
I'm following up on this one and will get back to you as soon as I have 
more information.

Thanks,
Josh, AdWords API Team

On Thursday, August 11, 2016 at 2:04:14 PM UTC-4, Josh Radcliff (AdWords 
API Team) wrote:
>
> Hi Zia,
>
> I see you already are discussing this issue with Mike on another post 
> , 
> so I'll mark this one a duplicate. Mike is still looking into this issue 
> for you and will respond on the other post.
>
> Thanks,
> Josh, AdWords API Team
>
> On Thursday, August 11, 2016 at 10:51:28 AM UTC-4, xtcsuk wrote:
>>
>> Hello,
>>
>> A question around a cancelled job, on getting result for a job, the data 
>> tells us the job has been cancelled, no downloadUrl and with the following 
>> stats:
>>
>> service call:
>> batchjobservice.get(selector).entries
>>
>> api call result:
>> estimatedPercentExecuted: 60%, numOperationsExecuted: 2, 
>> numOperationsSucceeded: 2, numResultsWritten: 0
>>
>> our record shows, 3 operations are attached to this job.
>>
>> The jobid = 341175452, and accountid = 8227096083
>>
>> Based on this, how would then we update our end of the bargain, with no 
>> downloadUrl, we can't do anything really, and surely that leaves us in 
>> unknown status.
>>
>>
>> regards,
>> Zia
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/6ab919ab-1ae2-4d24-8fea-774cef469402%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605

['Michael Cloonan (AdWords API Team)' via AdWords API Forum]

Hello,

I apologize for that; it was simply a misunderstanding.

I have reopened the other thread for us to track that issue separately, and 
we will be responding there once we've had a chance to look into it.

Regards,
Mike, AdWords API Team

On Friday, August 12, 2016 at 5:42:25 AM UTC-4, xtcsuk wrote:
>
> Thank you Mike,
>
> I posted another issue on the 11th of August titled "api version 201605 - 
> batchjobservice", but is marked as duplicate.  Can't open the thread 
> anymore, its taking me here:
> This is a different issue, we have downloadUrl, Done as job status, but 
> the stats does not reflect the total number of operations, not sure why 
> marked as duplicate, can provide the details again if needed.
>
> regards,
> Zia
>
> On Thursday, 11 August 2016 14:25:14 UTC+1, Michael Cloonan (AdWords API 
> Team) wrote:
>>
>> Hello,
>>
>> I will pass these IDs along to engineering so they can get the download 
>> URL to show properly.
>>
>> Regards,
>> Mike, AdWords API Team
>>
>> On Thursday, August 11, 2016 at 8:10:54 AM UTC-4, xtcsuk wrote:
>>>
>>> Hi Mike,
>>>
>>> Thanks for the clarification, looks like the empty download url bug 
>>> still persists, for a handful number of jobs, at least.  Here is the list 
>>> (been identified so far)
>>>
>>> JobId,   AccountId   Approximate 
>>> upload time
>>> 34100429769850537022016-08-11 
>>> 10:42:34.140
>>> 34065384486905392772016-08-11 
>>> 00:18:36.320
>>>
>>> regards,
>>> Zia
>>>
>>> On Tuesday, 9 August 2016 19:04:36 UTC+1, Michael Cloonan (AdWords API 
>>> Team) wrote:

 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:
>
> 

Re: api version 201605

[xtcsuk]

Thank you Mike,

I posted another issue on the 11th of August titled "api version 201605 - 
batchjobservice", but is marked as duplicate.  Can't open the thread 
anymore, its taking me here:
This is a different issue, we have downloadUrl, Done as job status, but the 
stats does not reflect the total number of operations, not sure why marked 
as duplicate, can provide the details again if needed.

regards,
Zia

On Thursday, 11 August 2016 14:25:14 UTC+1, Michael Cloonan (AdWords API 
Team) wrote:
>
> Hello,
>
> I will pass these IDs along to engineering so they can get the download 
> URL to show properly.
>
> Regards,
> Mike, AdWords API Team
>
> On Thursday, August 11, 2016 at 8:10:54 AM UTC-4, xtcsuk wrote:
>>
>> Hi Mike,
>>
>> Thanks for the clarification, looks like the empty download url bug still 
>> persists, for a handful number of jobs, at least.  Here is the list (been 
>> identified so far)
>>
>> JobId,   AccountId   Approximate 
>> upload time
>> 34100429769850537022016-08-11 10:42:34.140
>> 34065384486905392772016-08-11 00:18:36.320
>>
>> regards,
>> Zia
>>
>> On Tuesday, 9 August 2016 19:04:36 UTC+1, Michael Cloonan (AdWords API 
>> Team) wrote:
>>>
>>> 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 

Re: api version 201605 - batchjobservice

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Zia,

I see you already are discussing this issue with Mike on another post 
, so 
I'll mark this one a duplicate. Mike is still looking into this issue for 
you and will respond on the other post.

Thanks,
Josh, AdWords API Team

On Thursday, August 11, 2016 at 10:51:28 AM UTC-4, xtcsuk wrote:
>
> Hello,
>
> A question around a cancelled job, on getting result for a job, the data 
> tells us the job has been cancelled, no downloadUrl and with the following 
> stats:
>
> service call:
> batchjobservice.get(selector).entries
>
> api call result:
> estimatedPercentExecuted: 60%, numOperationsExecuted: 2, 
> numOperationsSucceeded: 2, numResultsWritten: 0
>
> our record shows, 3 operations are attached to this job.
>
> The jobid = 341175452, and accountid = 8227096083
>
> Based on this, how would then we update our end of the bargain, with no 
> downloadUrl, we can't do anything really, and surely that leaves us in 
> unknown status.
>
>
> regards,
> Zia
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/067587a8-1d4c-42b7-8640-a893cde617c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605

['Michael Cloonan (AdWords API Team)' via AdWords API Forum]

Hello,

I will pass these IDs along to engineering so they can get the download URL 
to show properly.

Regards,
Mike, AdWords API Team

On Thursday, August 11, 2016 at 8:10:54 AM UTC-4, xtcsuk wrote:
>
> Hi Mike,
>
> Thanks for the clarification, looks like the empty download url bug still 
> persists, for a handful number of jobs, at least.  Here is the list (been 
> identified so far)
>
> JobId,   AccountId   Approximate 
> upload time
> 34100429769850537022016-08-11 10:42:34.140
> 34065384486905392772016-08-11 00:18:36.320
>
> regards,
> Zia
>
> On Tuesday, 9 August 2016 19:04:36 UTC+1, Michael Cloonan (AdWords API 
> Team) wrote:
>>
>> 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 

Re: api version 201605

[xtcsuk]

Hi Mike,

Thanks for the clarification, looks like the empty download url bug still 
persists, for a handful number of jobs, at least.  Here is the list (been 
identified so far)

JobId,   AccountId   Approximate upload 
time
34100429769850537022016-08-11 10:42:34.140
34065384486905392772016-08-11 00:18:36.320

regards,
Zia

On Tuesday, 9 August 2016 19:04:36 UTC+1, Michael Cloonan (AdWords API 
Team) wrote:
>
> 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:

Re: api version 201605

['Michael Cloonan (AdWords API Team)' via AdWords API Forum]

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 

Re: api version 201605

[xtcsuk]

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 

Re: api version 201605

['Michael Cloonan (AdWords API Team)' via AdWords API Forum]

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 

Re: api version 201605

['Michael Cloonan (AdWords API Team)' via AdWords API Forum]

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/3a3d9ed9-a6fb-4892-99ff-daaf98780bad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605

[xtcsuk]

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/d2aa9d53-a730-45cc-88da-ae55699701e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605

['Michael Cloonan (AdWords API Team)' via AdWords API Forum]

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/8003c3e4-22d0-4d13-8421-3eefb13744a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605

[xtcsuk]

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/ec1dacec-d8aa-4363-b777-f276995fd689%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605

['Michael Cloonan (AdWords API Team)' via AdWords API Forum]

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/9b1da4ce-e1f9-4321-adb1-932dda9efe70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605

[xtcsuk]

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/bc98cd08-e2f1-443c-93d8-1e035ac90fb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605

['Peter Oliquino' via AdWords API Forum]

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/39149bba-83de-49a3-be5f-12c9b993439c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605

[xtcsuk]

Thanks Peter,

On downloadUrl property of the BatchJob entity, I was wrong in assuming it 
to have a value all the time, irrespective of the status (cancelled/done). 
 So yes, thanks for clarifying that.
On report sides, nothing has changed in criteria on our side, will keep an 
eye and will do as suggested.

regards,
Zia


On Monday, 1 August 2016 06:16:02 UTC+1, Peter Oliquino wrote:
>
> Hi Zia,
>
> Please see below my answers :
>
> 1. The report service (arbitrary report types) seems to time out more 
> frequently than v201601.  We have a retry logic in place, where these 
> errors are retried and they eventually succeed.
>
> *One possible cause of the timeouts would be that you are processing 
> extremely large reports as discussed here in our guide 
> . 
> If the issues persist, could you provide your complete report definition 
> and any logs produced when you ran the report?*
>
> 2. The new batch job service, seems to work fine, however on getting the 
> results, given a job id it returns a null value for the downUrl property, 
> again this happened in only a handful number of batches, say just 3 out of 
> 1000.
>
> *The downloadUrl is expected to be null while the batch job is still 
> processing, or is canceled. However, if the issue occured outside of those 
> conditions, could you provide your complete SOAP request and response so we 
> can investigate further? Also, I would recommend that you reply 
> using Reply privately to author if you will send any of the information 
> that I have requested from you.*
>
> Thanks and regards,
> 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/9d8ba25e-413c-429f-a475-6e7546f24b7b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: api version 201605

['Peter Oliquino' via AdWords API Forum]

Hi Zia,

Please see below my answers :

1. The report service (arbitrary report types) seems to time out more 
frequently than v201601.  We have a retry logic in place, where these 
errors are retried and they eventually succeed.

*One possible cause of the timeouts would be that you are processing 
extremely large reports as discussed here in our guide 
. 
If the issues persist, could you provide your complete report definition 
and any logs produced when you ran the report?*

2. The new batch job service, seems to work fine, however on getting the 
results, given a job id it returns a null value for the downUrl property, 
again this happened in only a handful number of batches, say just 3 out of 
1000.

*The downloadUrl is expected to be null while the batch job is still 
processing, or is canceled. However, if the issue occured outside of those 
conditions, could you provide your complete SOAP request and response so we 
can investigate further? Also, I would recommend that you reply 
using Reply privately to author if you will send any of the information 
that I have requested from you.*

Thanks and regards,
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/32c5742b-e580-41c0-86e3-0388a451618f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.