Hi folks,
I have been facing the same issue while running *ad_group_ad* Report. The
task seems to be getting stuck in running state for several hrs and
completes successfully only when rerun. This seems to be happening once in
a while and more often from the last week.
Is there any other fix
Hi all,
I'm a colleague of Nadine's on the Google Ads API Team and I have some updates
on the points she highlighted earlier.
1. The issues with product groups that Geoff mentioned. I have a teammate who's
taken point on sorting that one out.
2. A few timeouts on our back-end that we're
Hello Silvia,
Thank you for the information. I sent you a private email that you should see
that acknowledges I received it.
Regards,
Nadine Wang
Google Ads API Team
ref:_00D1U1174p._5004Q2aQjmG:ref
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
I replied with some customerIDs and batchJobIDs with slow running.
Thanks!
Il giorno mercoledì 18 maggio 2022 alle 19:46:25 UTC+2 adsapi ha scritto:
> Greetings All,
>
> Thank you for chiming in on this. It looks like we have multiple reasons
> at this time as to why a batch job could be either
Just chipping in here - we're seeing the same issue and are working with
the support team. A couple of notes on what we're seeing:
- It only appears to affect AdGroupCriterion operations. In our case, we're
creating product groups in Shopping campaigns. Where we submit operations
to create ad
Hello All,
Thank you for providing all the additional details. I'm currently working
through each of the messages sent to determine what specifically is causing the
issue for your individual batch jobs. I'll reply privately to each of you.
Regards,
Nadine Wang
Google Ads API Team
did the same!
Status stuck on Pending and we are getting kicked out of the /GetOperation
with a Task was cancelled error. not sure if someone is facing the same
issue here?
Le jeudi 19 mai 2022 à 16:28:17 UTC+2, Prototype.co a écrit :
> I've sent an e-mail with some customer and batch job
I've sent an e-mail with some customer and batch job ids.
adsapi a következőt írta (2022. május 18., szerda, 19:46:25 UTC+2):
> Greetings All,
>
> Thank you for chiming in on this. It looks like we have multiple reasons
> at this time as to why a batch job could be either stuck running or
Greetings All,
Thank you for chiming in on this. It looks like we have multiple reasons at
this time as to why a batch job could be either stuck running or slower than
expected.
First, there were general issues with Batch Jobs that were resolved on May
11th. We had a bit of a backlog, and we
Yes, we are still experiencing this issue. Note that some Batch Jobs seem
to run just fine (in our case, those that create a small number of ad
extensions and link them to campaigns or ad groups - a batch job like this
typically has 10-20 operations in total). However, Batch Jobs that update
Yes, we have the same issue on the long time of processing
Il giorno mercoledì 18 maggio 2022 alle 15:05:23 UTC+2 ska...@armis.tech ha
scritto:
> Is the issue still persisting on your side everyone?
>
> Le vendredi 13 mai 2022 à 16:26:54 UTC+2, adsapi a écrit :
>
>> Hello,
>>
>> Thanks for
Is the issue still persisting on your side everyone?
Le vendredi 13 mai 2022 à 16:26:54 UTC+2, adsapi a écrit :
> Hello,
>
> Thanks for your patience on this. Please allow me to share your experience
> with our team and I will provide an update shortly.
>
>
> Thanks,
> Matt
> Google Ads API
Hello,
Thanks for your patience on this. Please allow me to share your experience with
our team and I will provide an update shortly.
Thanks,
Matt
Google Ads API Team
Matt
Google Ads API Team
ref:_00D1U1174p._5004Q2aQjmG:ref
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find
Hi,
for us it looks like things got better today, but the overall time for each
process is much higher than in the past (20-30 minutes compared to the
maximum 1-2 minutes previously).
Do you think that batch processing will return to times closer to those of
the past?
Best,
Silvia
Il giorno
Unfortunately, we experienced no difference on our part. Batch Jobs are
still "running forever", and if we wait long enough, we end up with a
"DeadlineExceeded" error.
Do note that in some cases, the Batch Jobs run fine (for example, updating
and creating Asset-based extensions work just
Unfortunately, we experienced no difference on our part. Batch Jobs are
still "running forever", and if we wait long enough, we end up with a
"DeadlineExceeded" error.
Christian a következőt írta (2022. május 12., csütörtök, 22:02:55 UTC+2):
> Hi,
>
> for us it looks like things got better
Hi,
for us it looks like things got better today. Overall batch jobs got
processed in the usual time.
Thanks for the support and resolution.
Best,
Christian
On Thursday, May 12, 2022 at 12:01:55 PM UTC+2 Prototype.co wrote:
> Hi Team,
>
> We are also experiencing the same issue, Batch Jobs
Hi Team,
We are also experiencing the same issue, Batch Jobs seem to be running
forever, and the operations do not seem to be running in any way.
m.m...@doveconviene.com a következőt írta (2022. május 12., csütörtök,
10:46:01 UTC+2):
> Hi Team,
> on our side, we don't see any improvements at
Hi Team,
on our side, we don't see any improvements at the moment.
Batch jobs are still very slow,
Regards,
Matteo
On Thursday, 12 May 2022 at 10:30:31 UTC+2 ci...@channable.com wrote:
> Hi,
>
> We also still have batch jobs which have been running since yesterday.
> Also newly submitted
Hi,
the issue does not seem to have been solved for us.
Do you have any news?
Thanks
Silvia
Il giorno mercoledì 11 maggio 2022 alle 22:26:50 UTC+2 adsapi ha scritto:
> Hi Matteo,
>
> Thanks for your patience on this. This issue should be resolved now. Can
> you please retry your batch job
Hi,
the situation is becoming more and more difficult to manage.
Do you have any news on this problem?
Regards,
Matteo
On Tuesday, 10 May 2022 at 16:00:25 UTC+2 ska...@armis.tech wrote:
> is there any updates on this?
>
> Le lundi 9 mai 2022 à 10:59:39 UTC+2, jaume@channable.com a écrit :
>
is there any updates on this?
Le lundi 9 mai 2022 à 10:59:39 UTC+2, jaume@channable.com a écrit :
> Hi Google,
>
> Expanding a bit more on this issue, we actually have some customers that
> are "stuck" with 100 running BatchJobs (affecting different campaigns).
> This means that we can't do
Hi Google,
Expanding a bit more on this issue, we actually have some customers that
are "stuck" with 100 running BatchJobs (affecting different campaigns).
This means that we can't do anything for them anymore unless we use the API
directly, which, as mentioned by our google partner, is not a
Hi,
Over the weekend the problem has only gotten worse and we now have over
2000 batch jobs stuck in the RUNNING state since at least yesterday
morning, May 8th.
I already supplied you a list of the affected batch job ids and customer
ids from before the weekend, but I can give you an updated
Hi,
We are facing the same issue since May 5. Today (May 8), we see batch jobs
in state RUNNING since May 6:
SELECT batch_job.id, batch_job.status,
batch_job.metadata.creation_date_time,
batch_job.metadata.estimated_completion_ratio FROM batch_job WHERE
batch_job.status != DONE ORDER BY
Hi,
We've replied with some logs as well.
Also, we are over 2000 BatchJobs for different customers that are in this
state right now...
We have seen that one of the affected BatchJobs (with 7 CREATE AdGroupAd
operations!) finished after 48 hours.
So it seems to be that it's just very slowly
Hi,
I sent the request/response privately, I'm not sure if it was well received?
do you have an update on this issue as it's blocking our business
operations!
Le jeudi 5 mai 2022 à 17:28:01 UTC+2, adsapi a écrit :
> Hello Everyone,
>
> Thanks for reaching out to the Google Ads API Forum.
>
>
Hey again,
To add on this issue, currently even with 400 operation, the batch job
service is having issues.
This is an example of a response I'm currently receiving:
Request --- MethodName: google.longrunning.Operations/GetOperation
Endpoint: googleads.googleapis.com:443
Headers:
Hi Google Team,
We currently have over 1300 batch jobs for multiple client customer ids
with this issue.
They do not leave the RUNNING state so we do not know whether we can
resubmit a new batch job, without it leading to duplicate objects in their
Google Ads accounts.
If you can confirm
Hello,
We are having the same issue since yesterday but especially for a large
chunk of operations.
If we launch with less than 2000 operations in a batch, it works properly.
This is blocking our operations, can you confirm that it is a bug from your
side?
Thanks,
Skander
Le jeudi 5 mai
Hello,
we have noticed that since yesterday, some of the Batch Jobs we pushed
through the GoogleAds API are not finishing.
We are seeing an increased amount of BatchJobs in this status that have
been on the RUNNING status for over 8 hours. And we don't know how to react
and deal with them.
31 matches
Mail list logo
