api version 201605 - batchjobservice

[xtcsuk]

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: 20000, numOperationsSucceeded: 20000, numResultsWritten: 0

our record shows, 30000 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

[Josh Radcliff (AdWords API Team)]

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

[Josh Radcliff (AdWords API Team)]

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

[Josh Radcliff (AdWords API Team)]

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

[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

[Josh Radcliff (AdWords API Team)]

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.

        <entries>

          <id>341175452</id>

          <status>CANCELED</status>

          <progressStats>

            <numOperationsExecuted>20000</numOperationsExecuted>

            <numOperationsSucceeded>20000</numOperationsSucceeded>

            <estimatedPercentExecuted>66</estimatedPercentExecuted>

            <numResultsWritten>0</numResultsWritten>

          </progressStats>

          <downloadUrl>

            <url>https://batch-job-download-prod...</url>

            <expiration>20160911 170333 Etc/GMT</expiration>

          </downloadUrl>

        </entries>

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

Thanks,

Josh, AdWords API Team

[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 id            account id

342115475     7653799969

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

Appreciating the verification on this one, please.

regards,

Zia

[Josh Radcliff (AdWords API Team)]

Hi Zia,

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

Thanks,

Josh, AdWords API Team

[Josh Radcliff (AdWords API Team)]

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

[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

[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

[Thanet Knack Praneenararat (AdWords API Team)]

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

[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

[Josh Radcliff (AdWords API Team)]

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

[Josh Radcliff (AdWords API Team)]

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

[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

[Josh Radcliff (AdWords API Team)]

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

[xtcsuk]

Thanks Josh, much appreciated.

regards,

Zia

[Josh Radcliff (AdWords API Team)]

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 downloadUrls. I expect to see more improvements over the coming weeks as well.

Thanks,

Josh, AdWords API Team

[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

[Josh Radcliff (AdWords API Team)]

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