Hello Nadine, thanks for your effort and your solution!
I already created and deleted product partitions in past, but I never had these problems before. I never recognized that the order in the request was relevant, I always thought it's sufficent to keep a consistent state after a request. Therefore my question: was something changed on product partition's server side or have I just been lucky by not running into these problems so far? (I changed my task collector from List to Set so it's absolutely possible, that request's operation order changed) Regards, Christian Am Donnerstag, 8. Februar 2018 16:03:35 UTC+1 schrieb Nadine Sundquist (AdWords API Team): > > Hello Christian, > > Thanks for providing all those details. That really helped me figure out > what's going on. I'm just following up on the forum, so anyone else who > bumps into this in the future can be helped out as well. I noticed in your > logs that the first removes were happening just fine and later it became > more frequent. So, I looked at the path of your tree that was being > removed. What was happening is that you were trying to remove a leaf node > after you had already removed a higher node in the tree earlier in the same > request. That's why the errors were happening. It was telling you that you > had already removed an item further up in the tree, so the item you were > trying to remove now no longer existed. Here's an example. Let's say you > have: > > 1234 * / product type = "haus & garten" / product type = > "heimtextilien" / product type = "frottierwaren" / product type = > "duschtuch" / brand = "vossen" / > 5678 * / product type = "haus & garten" / product type = > "heimtextilien" / product type = "frottierwaren" / product type = > "duschtuch" / brand = "vossen" / item id = * > > You remove the first one 1234. Then, you try to remove the second one > 5678. The second one would error because the the first remove call would > have wiped out the second one already. Trees are a tricky business. Many of > our client libraries have utilities > <https://developers.google.com/adwords/api/docs/samples/java/shopping-campaigns> > to > handle these trees because of odd situations like this one. > > Cheers, > Nadine, AdWords API Team > > On Wednesday, February 7, 2018 at 1:00:38 PM UTC-5, Sreelakshmi Sasidharan > (AdWords API Team) wrote: >> >> Hi Christian, >> >> What you have explained is the correct approach to identify the product >> partition. To take a closer look at the issue, could you please enable >> logging and share the SOAP request and response logs? You can use reply >> privately to author while sharing the details. >> >> Thanks, >> Sreelakshmi, 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 [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/6cc68e6a-bd1f-4835-ab26-b2beea4b6c02%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
