subject:"Re\: api version 201605 \- batchjobservice"

Re: api version 201605 - batchjobservice

2016-10-18 Thread '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

2016-09-19 Thread 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

2016-09-09 Thread '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

2016-08-25 Thread 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

2016-08-24 Thread '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

2016-08-24 Thread 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

2016-08-23 Thread '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

2016-08-23 Thread '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

2016-08-23 Thread 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

2016-08-17 Thread '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

2016-08-17 Thread 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

2016-08-17 Thread 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

2016-08-16 Thread '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 - batchjobservice

2016-08-15 Thread '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

2016-08-15 Thread 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

2016-08-15 Thread '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

2016-08-15 Thread 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

2016-08-12 Thread '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 - batchjobservice

2016-08-12 Thread '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 - batchjobservice

2016-08-11 Thread '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 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

Re: api version 201605 - batchjobservice

20 matches

Site Navigation

Mail list logo

Footer information