Hi Wesley, Thank you for your patience here.
Allow me to share the update that I received from the team. Instead of using Batch Job, I would suggest to explore GoogleAdsService::Mutate so that you don't have to wait for the batch job to cancel when you are encountering errors. If this workaround is not suitable on your use case, then please provide more details to why you need this feature. Also, you can provide the complete request <https://developers.google.com/google-ads/api/docs/concepts/field-service#request> and response <https://developers.google.com/google-ads/api/docs/concepts/field-service#response> logs, along with the request-id <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id>, so that we can investigate the issue. You can provide it via Reply privately to author option. If this option is not available, then send it instead on this email address [email protected]. Regards, Ernie John B. Tacata Google Ads API Team On Monday, January 31, 2022 at 4:44:51 PM UTC+8 Google Ads API and AdWords API Forum wrote: > Reposting the last inquiry (link to actual inquiry > <https://groups.google.com/g/adwords-api/c/XTcuKNlrrRY/m/bpUAU1h8CQAJ>) > from the forum as it wasn't routed to our support queue. > > Cheers, > > Ernie John B. Tacata > > *Google Ads API Team* > On Friday, January 28, 2022 at 3:20:16 PM UTC+8 [email protected] > wrote: > >> Just wanted to follow up here. We recently ran into an >> `InternalServerError` that we received from the API when trying to upload >> operation to a batch job. Because of this, we now have a `PENDING` batch >> job, and as far as we can tell, there is no way to get rid of this batch >> job because we cannot cancel it. >> >> It seems quite the oversight to not allow canceling the batch job when >> users can get into this situation by errors thrown by the Google Ads API. >> >> It is also not robust to just "pick up where you left off" in the batch >> job, because depending on when the error happened, it currently seems >> impossible to know which operations are actually uploaded (I believe we can >> only get the number and not the operations themselves). >> >> Is there anything we can do here besides abandoning the batch job and >> hoping that we don't keep getting Internal Server Errors resulting in us >> reaching the limit of the amount of batch jobs we can have "active"? >> >> On Friday, October 22, 2021 at 7:17:10 AM UTC+2 adsapi wrote: >> >>> Hi Miquel, >>> >>> Thank you for your reply. I will also share your latest response to the >>> feature request that I've created. Yes, please follow our blog >>> <https://ads-developers.googleblog.com/search/label/google_ads_api> for >>> the meantime. >>> >>> Let me know also if you have further questions. >>> >>> >>> Regards, >>> [image: Google Logo] >>> Ernie John Blanca Tacata >>> Google Ads API Team >>> >>> >>> ref:_00D1U1174p._5004Q2QDj4r: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 [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 "Google Ads API and AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/b6484430-65cb-4918-806a-121d2b4bfc16n%40googlegroups.com.
