Hi Peter,
Are you still experiencing this issue, and if so, how frequently?
As suspected, this was due to retries within our services, but
unfortunately I don't have a great solution on how to detect this
particular scenario, so I'm curious to know if this is still having a large
impact for yo
Hi Peter,
I still don't have an update, unfortunately. I've reached out to the
engineers again and will let you know when I get a response.
Thanks,
Josh, AdWords API Team
On Wednesday, December 9, 2015 at 5:00:49 AM UTC-5,
peter.rietz...@smarter-ecommerce.com wrote:
>
>
> Sorry for bothering a
Sorry for bothering again - still no updates on this ?
Thanks!
Peter
Am Mittwoch, 18. November 2015 16:11:08 UTC+1 schrieb Josh Radcliff
(AdWords API Team):
>
> Hi Peter,
>
> No updates yet, but the engineers are looking into it. I'll get back to
> you as soon as I hear anything.
>
> Cheers,
Hi Peter,
No updates yet, but the engineers are looking into it. I'll get back to you
as soon as I hear anything.
Cheers,
Josh, AdWords API Team
On Tuesday, November 17, 2015 at 11:25:13 PM UTC-5,
peter.rietz...@smarter-ecommerce.com wrote:
>
> Hi Josh
>
> Any updates on this ?
>
> Thanks!
> P
Hi Josh
Any updates on this ?
Thanks!
Peter
Am Mittwoch, 11. November 2015 20:55:04 UTC+1 schrieb Josh Radcliff
(AdWords API Team):
>
> Hi Peter,
>
> Using that request ID, I found some information on our side that indicates
> that there may have been an unexpected duplication of this request.
Hi Peter,
Using that request ID, I found some information on our side that indicates
that there may have been an unexpected duplication of this request. I'm
following up with the service owners to see what happened here, and will
let you know as soon as I hear back from them.
Thanks,
Josh, AdW
Hi
No, I can't see any logs in our system despite the fact that the request
has failed - but those logs were logged a few minutes later because further
request were logged aggregated by our application.
The first example (PRODUCT_PARTITION_ALREADY_EXISTS from 30.10.2015) that
I've posted to
Hi,
I took a look at the requests coming from your developer token, and I see
REMOVE mutate requests coming in for that ad group's criteria at the
following times:
ViennaTime : 2015-10-30 06:05:40
Successful : True
ViennaTime : 2015-10-30 06:06:04
Successful : False
In the user interface, I s
Hi Josh
These are really wild assumptions, but for me it looks like that I can see
the same problem with other requests regarding shopping ad group criterions
too.
I've got another case that looks pretty similar to me (though I cannot
prove this since I do not have SOAP logs for this). But f
i Josh
Our app definitely mutates trees in parallel - but it never mutates trees
in parallel belonging to the same campaigns. The requests that I sent
before were reproduced in a single-threaded sandbox. The requests you
mention are requests that our app tries to send once a day exactly be
Hi Peter,
Are you running multiple threads that are mutating the trees in question? I
ask because I looked at two of your requests from today that failed
with PRODUCT_PARTITION_ALREADY_EXISTS followed
by PRODUCT_PARTITION_DOES_NOT_EXIST, and in both cases the partition in
question *does* alrea
Hi Josh
Could the usage of not using distinct temporary IDs cause this problem ? As
stated above, 99% of my requests succeed (and we've actually sent millions
of them until now).
The tree is correct for our purposes. It will be changed by other requests
later on. The problem doesn't seem to b
Hi,
I noticed that your request is operating on two ad groups but you are
reusing the same temporary ID for both. I would recommend using distinct
temporary IDs for distinct *Biddable/NegativeAdGroupCriterion* within a
single request.
Also, in each case you are constructing what looks like an
It looks like that we have the same problem.
We create a brand new AdGroup, then send the following request:
https://adwords.google.com/api/adwords/cm/v201506";>
ADD
https://adwords.google.com/api/adwords/cm/v201506";
xsi:type="ns2:BiddableAdG
Hi,
Since you are using the AdGroupCriterionService, do you mean AdGroup
instead of campaign? Could you please send me both your SOAP request and
response for the successful and failed operations through *Reply privately
to author*? This will help me see why it is working for one and not the
Thanks for your response .
If my account don't have any active/paused campaign, in the case the code
works and if account already have a active/paused campaign then doesn't
work .
On Tuesday, October 6, 2015 at 12:39:55 AM UTC+5:30, Anthony Madrigal wrote:
>
> Hi,
>
> You said that sometimes t
Hi,
You said that sometimes this code works for you. In what instances does it
work? Could you also provide me through *Reply privately to author *your
SOAP request and response where you are getting these errors?
Thanks,
Anthony
AdWords API Team
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=
During product partition in a newly created adgroup, getting error(some times
the code works and other time it gives an error)
Server raised fault: '[AdGroupCriterionError.PRODUCT_PARTITION_ALREADY_EXISTS @
operations[0].operand.criterion,
AdGroupCriterionError.PRODUCT_PARTITION_DOES_NOT_EXIST
18 matches
Mail list logo
