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 good option
with our use cases.
Hope this can be resolved soon.
Jaume
On Monday, May 9, 2022 at 8:29:39 AM UTC+2 Ciel Eijssen wrote:
> 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 list if needed.
>
> Appreciate your time.
>
> Best,
> Ciel
>
> On Sunday, May 8, 2022 at 9:04:20 PM UTC+2 Christian wrote:
>
>> 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 batch_job.metadata.creation_date_time
>> LIMIT 4
>>
>> batch_job {
>> resource_name: "customers/50.....307/batchJobs/9016872863
>> <(901)%20687-2863>"
>> metadata {
>> creation_date_time: "2022-05-06 06:23:50"
>> estimated_completion_ratio: 0.0
>> }
>> status: RUNNING
>> id: 9016872863 <(901)%20687-2863>
>> }
>>
>> batch_job {
>> resource_name: "customers/50.....307/batchJobs/9016708636
>> <(901)%20670-8636>"
>> metadata {
>> creation_date_time: "2022-05-06 06:23:51"
>> estimated_completion_ratio: 0.0
>> }
>> status: RUNNING
>> id: 9016708636 <(901)%20670-8636>
>> }
>>
>> batch_job {
>> resource_name: "customers/50.....307/batchJobs/9020761205"
>> metadata {
>> creation_date_time: "2022-05-06 12:33:30"
>> estimated_completion_ratio: 0.0
>> }
>> status: RUNNING
>> id: 9020761205
>> }
>>
>> batch_job {
>> resource_name: "customers/50.....307/batchJobs/9030551684"
>> metadata {
>> creation_date_time: "2022-05-07 12:14:41"
>> estimated_completion_ratio: 0.0
>> }
>> status: RUNNING
>> id: 9030551684
>> }
>>
>> Is the job Id sufficient to investigate this on your side or should I
>> send the customer ID in private as well?
>>
>> Thanks for your support.
>>
>> Best,
>> Christian
>> On Friday, May 6, 2022 at 4:29:50 PM UTC+2 jaume....@channable.com wrote:
>>
>>> 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 being processed, but
>>> waiting for 48hours doesn't seem like a good approach.
>>>
>>> Hope to hear from you,
>>> Thanks.
>>>
>>> On Friday, May 6, 2022 at 2:50:35 PM UTC+2 ska...@armis.tech wrote:
>>>
>>>> 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.
>>>>>
>>>>> I can see that you are all having issues with BatchJobs requests.
>>>>> However, could you please provide us with the complete *request*
>>>>> <https://developers.google.com/google-ads/api/docs/concepts/field-service?hl=en#request>
>>>>>
>>>>> and *response*
>>>>> <https://developers.google.com/google-ads/api/docs/concepts/field-service?hl=en#response>
>>>>>
>>>>> logs with the *request-id*
>>>>> <https://developers.google.com/google-ads/api/docs/concepts/call-structure?hl=en#request-id>
>>>>>
>>>>> generated for the BatchJobs requests where we can see said observed
>>>>> behavior via the *Reply privately to author* option, so I can report
>>>>> this to my rest of the team?
>>>>>
>>>>> For the client library, logging can be enabled by navigating to the
>>>>> Client libraries > Your client library (ex Java) > Logging documentation,
>>>>> which you can access from this link
>>>>> <https://developers.google.com/google-ads/api/docs/client-libs>.
>>>>>
>>>>> Regards,
>>>>> [image: Google Logo]
>>>>> Yasar
>>>>> Google Ads API Team
>>>>>
>>>>>
>>>>> ref:_00D1U1174p._5004Q2aQjmG:ref
>>>>>
>>>>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/c338a156-44e7-41ea-b406-9224f8712d53n%40googlegroups.com.
