Hello everyone,
Thanks for your patience during this issue. All backed up batch jobs have
been processed and we are back to operating normally.
I apologize for the inconvenience. If anyone else starts running into this
issue again, please let me know.
Thanks,
-Mike, AdWords API Team
On Thursd
Hello,
The same problem from yesterday has recurred this morning. Yesterday, we
did eventually work through all the jobs in the queue, and the same will
happen today while engineering works to determine the root cause.
If you have a job stuck at 0%, do not cancel it and retry it. Please
instea
We are still unable to process jobs. This is very crucial for our business.
Please help!!!
FYI: MutateJobService is still working although it is slow. Please do not
discontinue MutateJobService unless BatchJobService is working properly!
On 27 Aug, MutateJobService will sunset which is a very b
Michael, seeing as we have jobs that have been at 0% for hours on end,
would you recommend keeping them waiting or cancelling them and
re-submitting?
On Wednesday, July 20, 2016 at 5:21:42 PM UTC+2, Michael Cloonan (AdWords
API Team) wrote:
>
> Hello,
>
> Engineering has found the root cause o
I send some new jobs to queue.
All have status ACTIVE and percent 0.
IDs:
327104183,
327103697,
327103541,
327102302,
327102209,
327101831,
327101810,
327049528,
327049516,
327049510,
327049492,
327049489,
327049471,
327049159,
327048802,
327048790,
327048760,
327048298,
327048274,
327048136,
327
We were also seeing lots of batch jobs running indefinitely. Today morning,
the situation seems a little better, but we are still having problems with
jobs running without progress.
Some of the jobs running longer than 20 minutes with 2,000 elements each:
327058106
327004624
327016504
327007494
I have the same issue. My jobs has status ACTIVE with 0 percent from 30
minutes.
JobIDs : 327017976, 327090161
Yesterday, none of my job was done.
W dniu poniedziałek, 2 maja 2016 15:32:47 UTC+2 użytkownik
domenico@kaufda.de napisał:
>
> Hello everyone,
> it is since last night we are exper
Hello Michael,
Thank you for solving the problem.
Would it be possible to have some technical insights about the problem?
Would love to know what's happening behind the scenes :)
Best,
S-
On Wednesday, July 20, 2016 at 5:21:42 PM UTC+2, Michael Cloonan (AdWords
API Team) wrote:
>
> Hello,
>
Hello,
Engineering has found the root cause of the issue and jobs are being
processed again now. Please note that there is a very large backlog of jobs
from the duration of the issue, so it may take some time for your specific
jobs to be handled. Engineering and I will both continue to monitor
Another batch job ID: 326763413. It contains only 8 operations and has been
ACTIVE at 0% for around half an hour now.
On Wednesday, July 20, 2016 at 5:10:37 PM UTC+2, an...@clicksco.com wrote:
>
>
> Having the same issue here too
>
>
> On Wednesday, 20 July 2016 15:52:49 UTC+1, Michael Cloonan (A
Having the same issue here too
On Wednesday, 20 July 2016 15:52:49 UTC+1, Michael Cloonan (AdWords API
Team) wrote:
>
> Hello,
>
> Engineering is currently investigating the issue and I will update here as
> soon as I have more to share. Thanks for the reports, everyone.
>
> Regards,
> Mike, A
Hello,
Engineering is currently investigating the issue and I will update here as
soon as I have more to share. Thanks for the reports, everyone.
Regards,
Mike, AdWords API Team
On Wednesday, July 20, 2016 at 10:25:35 AM UTC-4, Brian Bachtel wrote:
>
> A batch job ID, 326746595
>
> On Wednesday
A batch job ID, 326746595
On Wednesday, July 20, 2016 at 9:38:34 AM UTC-4, Michael Cloonan (AdWords
API Team) wrote:
>
> Hello,
>
> I will pass this information along to engineering. A batch job ID would
> help immensely.
>
> I will post here when I have anything to report about this.
>
> Regard
Having the same issue. Created a new job with only 2 operations and it is
hanging in the ACTIVE state along with the rest of my jobs.
On Wednesday, July 20, 2016 at 8:06:19 AM UTC-4, Dorian Kind wrote:
>
> Just here to confirm that—since this morning the BatchJob service doesn't
> show any progr
Hello,
I will pass this information along to engineering. A batch job ID would
help immensely.
I will post here when I have anything to report about this.
Regards,
Mike, AdWords API Team
On Wednesday, July 20, 2016 at 8:06:19 AM UTC-4, Dorian Kind wrote:
>
> Just here to confirm that—since thi
Just here to confirm that—since this morning the BatchJob service doesn't
show any progress for any submitted jobs. As an example, I currently have a
job with ~40'000 operations that has been at 0% progress for the last hour.
Would job IDs help to diagnose this issue?
On Wednesday, July 20, 201
Hello,
this morning some BatchJobs are extremely slow.
Usually cancelling and resubmitting the job did the trick but now even that
doesn't work.
One example is the BatchJob with Id "326707007" it only contains 1
operation:
{u'operator': u'ADD', u'operand': {u'status': u'ENABLED', u'name':
u'1
Hello,
We are continually working to improve the performance of the
BatchJobService. Reports like these really help narrow down specific
problems, but since our progress on improvement is incremental, we aren't
able to update here every time something changes. Know that we take these
reports s
Hello Michael,
Is there an update about this?
Best,
Stefano-
On Tuesday, May 3, 2016 at 5:56:02 PM UTC+2, Michael Cloonan (AdWords API
Team) wrote:
>
> Hello,
>
> Engineering has found the root cause of this issue. Upon further
> investigation, it seems that in all these cases the job execu
Thanks for taking care and feedbacks
Regards
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received th
Hello,
Engineering has found the root cause of this issue. Upon further
investigation, it seems that in all these cases the job executes quite
quickly once it begins, but sits in the queue for quite some time before it
is able to start. We are working on improving the time it takes to start an
FWIW today I'm not getting any slowjobs.
On Tuesday, May 3, 2016 at 3:38:38 PM UTC+2, Michael Cloonan (AdWords API
Team) wrote:
>
> Hello,
>
> A few people responded with information, which I have forwarded to our
> engineering team to investigate more thoroughly. I will let you know when I
> h
Hello,
A few people responded with information, which I have forwarded to our
engineering team to investigate more thoroughly. I will let you know when I
hear something back.
Regards,
Mike, AdWords API Team
On Monday, May 2, 2016 at 2:33:40 PM UTC-4, domenico.scalamo...@kaufda.de
wrote:
>
> S
Sent privately the required data
Regards
On Monday, 2 May 2016 19:15:36 UTC+2, Michael Cloonan (AdWords API Team)
wrote:
>
> Hello,
>
> Could everyone experiencing issues with slowness in their batch jobs
> please provide me an example batch job that is having issues?
>
> Please provide both th
Hello,
Could everyone experiencing issues with slowness in their batch jobs please
provide me an example batch job that is having issues?
Please provide both the customer ID and the batch job ID for the job.
Regards,
Mike, AdWords API Team
On Monday, May 2, 2016 at 11:52:28 AM UTC-4, Hunter wr
We are also experiencing this issue as of this morning. Our BatchServiceJob
jobs stay at 0% completed, and then time out.
Thanks,
Hunter.
On Monday, May 2, 2016 at 9:32:47 AM UTC-4, domenico@kaufda.de wrote:
>
> Hello everyone,
> it is since last night we are experiencing many batch-jobs ru
You could implement some logic that cancels the jobs and resubmit it if 0
operations are executed after X seconds.
But yeah, hope this is solved asap by Google.
On Monday, May 2, 2016 at 4:00:16 PM UTC+2, domenico@kaufda.de wrote:
>
> Hi Stefano, thanks for the tips.
> At the moment we are d
Hi Stefano, thanks for the tips.
At the moment we are doing the same by manually restarting the jobs.
In general the problem is that we have many jobs running at any time in the
24h (some of them are critical) so we cannot manually restart them all
every time.
Hope the problem will be fixed soon
Hello,
I'm experiencing the same so after a while I cancel the job and retry which
is working "fine" for now.
(Tip: just wait for the job's status to be "CANCELING" and not "CANCELED"
because that also takes ages!).
Of course this is just a stopgap solution...waiting a couple of minutes for
2
Hello everyone,
it is since last night we are experiencing many batch-jobs running very
slow (in some cases completing after 30 minutes) in other cases hanging
indefinitely.
The problem is occurring also now.
Can this problem be fixed as soon as possible?
Thanks and regards
--
--
=~=~=~=~=~
30 matches
Mail list logo
