Hi Christian,

We have an ongoing issue at our end that causes the error you are seeing. 
I'll update this thread with more details as I hear from the team.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Tuesday, July 25, 2017 at 12:20:11 PM UTC-4, Christian wrote:
>
> Hi,
>
> recently we recognized some batch job issues. More precise, we see 3 
> problems:
>
> 1) Strange progress stats
>
>    id = 535340862
>    status = "DONE"
>    progressStats = 
>       (ProgressStats){
>          numOperationsExecuted = 0
>          numOperationsSucceeded = 0
>          estimatedPercentExecuted = 0
>          numResultsWritten = 7414
>       }
>    downloadUrl = ...
>
>
> The linked result file indeed contains 7414 entries which indicate a 
> successful execution of operations. *numOperationsExecuted* etc. and the 
> other stats do not reflect that.
>
> 2) Missing download URL
>
>    id = 535178174
>    status = "DONE"
>    progressStats = 
>       (ProgressStats){
>          numOperationsExecuted = 25000
>          numOperationsSucceeded = 25000
>          estimatedPercentExecuted = 100
>          numResultsWritten = 25000
>       }
>    ... no download url ...
>
>
> Obviously this is problematic as we cannot process results.
>
> 3) Duplicates in result files
>
>    id = 535170169
>    status = "DONE"
>    progressStats = 
>       (ProgressStats){
>          numOperationsExecuted = 25000
>          numOperationsSucceeded = 25000
>          estimatedPercentExecuted = 100
>          numResultsWritten = 45000
>       }
>    downloadUrl = ...
>
>
> Looking into the linked result file, many results indeed are reported 
> twice (for instance setting bid modifier on criterion 503006 in ad 
> group 41233022792 to 0.75). Duplicates are not following each other 
> directly, so it is not easy to filter them w/o maintaining a lookup for all 
> seen results in memory. Also, with regard to this example, it is *not* 
> the case that results are unique within the first 25000 results. Then we 
> could simply discard the rest. Duplicates can be found already within the 
> first 25000 result entries.
>
> The first issue is not that problematic since we can treat the result file 
> as the authority. However, issue 2 and 3 are real problems for us.
>
>
> Thanks in advance for any support on these issues!
>
> Best,
> Christian
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 [email protected].
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/5dc79664-4960-441c-a362-363c40236dec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • Broken batch jo... Christian
    • Re: Broken... 'Anash P. Oommen (AdWords API Team)' via AdWords API Forum
      • Re: Br... 'Anash P. Oommen (AdWords API Team)' via AdWords API Forum

Reply via email to