Hi All, Thank you for the additional information, which I've passed on to the core engineering team. I believe they have located the source of the problem, but I'm not sure when the fix will be ready.
Best, - Eric On Jan 24, 4:44 am, "pankaj (cs1050171)" <lpank...@gmail.com> wrote: > Hi Eric, > Replying on behalf of Hemchand, > The request id is "17f3ec7c550e6f28b10189bd92b1b2b0" for a similar > scenario. > Here we tried to pause the keywords and the changes got updates on > AdWords UI after some delay. > Although, the response was consistent in all cases. > > On Jan 19, 4:56 am, AdWords API Advisor <adwordsapiadvi...@google.com> > wrote: > > > > > > > > > Hi Hemchand, > > > Can you post the request ID of such a request so I can further > > investigate the problem? > > > Best, > > - Eric > > > On Jan 15, 2:35 am, Hemchand <hthalanch...@clickable.com> wrote: > > > > Hi Eric > > > > We are facing the same issue for Keyword Mutates. Status & Bid changes > > > are not getting reflected quickly on Adwords. Also the response we are > > > getting is quite erratic. While we tried to change the status of > > > multiple keywords to "Active", the response for all the keywords came > > > as paused, while on Adwords few of them are shown as active and some > > > still paused. This can cause major data inconsistencies at our end. > > > > -Hemchand > > > > On Jan 15, 2:50 am, AdWords API Advisor <adwordsapiadvi...@google.com> > > > wrote: > > > > > Hi MM, > > > > > I'm not sure how the web interface uses caching, but that could be a > > > > dead end. Unfortunately I don't have any advice for this situation, > > > > but let us know if you see this happen more frequently. > > > > > Best, > > > > - Eric > > > > > On Jan 14, 10:47 am, mm <margaret.a.mar...@gmail.com> wrote: > > > > > > Thanks Eric - > > > > > Would the browser be caching by account? IOW, since other accounts > > > > > didn't show this latency, would that knock browser caching off the > > > > > list of candidates for the problem's source? FWIW, we appeared to be > > > > > seeing a similar latency when viewing the account through AdWords > > > > > Editor, also. It has since resolved itself, so it's not really an > > > > > issue now, I'm just trying to get a feel for what can be done about > > > > > this if I see it again in the future. > > > > > > Thanks a bunch! > > > > > mm > > > > > > On Jan 14, 8:48 am, AdWords API Advisor <adwordsapiadvi...@google.com> > > > > > wrote: > > > > > > > Hi MM, > > > > > > > I haven't encountered this problem before, but if the API is > > > > > > returning > > > > > > the correct values then it sounds like more of an issue with the web > > > > > > interface. I'd double check that the issue isn't related to browser > > > > > > caching. > > > > > > > Best, > > > > > > - Eric Koleda, AdWords API Team > > > > > > > On Jan 12, 5:25 pm, mm <margaret.a.mar...@gmail.com> wrote: > > > > > > > > Hey guys - > > > > > > > I am running some updates to some keyword urls which appear to run > > > > > > > fine (no exception thrown, the Criterion in the return value list > > > > > > > all > > > > > > > have the new urls in them). However, when I go into the web UI to > > > > > > > look > > > > > > > at these changes, they aren't reflected for a long time (30 > > > > > > > minutes or > > > > > > > more). This appears account-specific - the changes are showing up > > > > > > > fine > > > > > > > in other accounts. Is there something that can be done to address > > > > > > > this? > > > > > > > > Thanks - > > > > > > > mm -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
