Hi Eric,
Thank you for your answer. I want find some solution for our
application if there is similar issue in the future, so I want to ask
you some additional questions:
1. Can you tell me what do you mean by large batches? Are we talking
about changes in hundreds, thousands, ten thousands entities? I'd like
to know where do you advice to put threshold for using bulk operations
over of their synchronous version.
2. What actually happened to the bulk requests which were successfully
posted to AdWords services? Were they eventually processed? Our users
lost patient with the application and simply terminated posting
changes and tried to post changes once again. That means multiple same
bulk operation requests were sent to AdWords services.
3. Is there some way how to manage bulk operations which were already
sent to AdWords services? I'm looking for something which will allow
me to cancel sent request, if it is not processed after some period of
time.
Cheers,
Marian
On May 26, 3:53 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:
> Hi Marian,
>
> The problem is only affecting the BulkMutateJobService, so using the
> synchronous methods is a viable workaround. In general we recommend
> using the BMJS only for large batches of work that are not very time
> sensitive, and using the synchronous services for smaller request or
> those that need to be processed immediately.
>
> Best,
> - Eric
>
> On May 26, 4:23 am, Tiny <marian.ti...@gmail.com> wrote:
>
>
>
> > Hi Eric,
>
> > Do you know whether the solution/workaround is using synchronous API
> > call instead of Bulk operations for now? We are using just bulk
> > operations at this moment but switching to synchronous operations
> > shouldn't be problem for us, if we know that it helps.
>
> > Thanks, Marian
>
> > On May 26, 12:04 am, AdWords API Advisor
>
> > <adwordsapiadvi...@google.com> wrote:
> > > Hi All,
>
> > > The core engineering team is looking into this issue, and I'll update
> > > this thread when I have more information.
>
> > > Best,
> > > - Eric Koleda, AdWords API Team
>
> > > On May 25, 3:40 pm, Inah from Brazil <inahmart...@gmail.com> wrote:
>
> > > > What is happening with the API? just keep the status job.getStatus ().
> > > > equals ("PENDING") ... Anybody know how to solve?
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords 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
