Is this happening for all waves the robot is on, or just the long ones? There is a bug that affects all waves: http://code.google.com/p/google-wave-resources/issues/detail?id=278&q=label%3AApiType-Robots%20label%3AType-Defect&colspec=Stars%20ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20Internal
But if it's just wave-specific, then this seems like potentially a different bug. - pamela On Fri, Oct 30, 2009 at 4:27 PM, Silicon Dragon <sdr...@gmail.com> wrote: > An official response for this issue (ack/deny) would be really appreciated > > Thank you, > -SDr > > > On Fri, Oct 30, 2009 at 2:41 AM, Silicon Dragon <sdr...@gmail.com> wrote: > >> Hi, >> >> For several, content-rich waves with high number of editors, robots are >> not receiving any notifications whatsoever. >> Steps to reproduce: >> >> 1, open >> https://wave.google.com/wave/#restored:wave:googlewave.com!w%252BfkhgC1biA >> 2, add any robot listening to WAVELET_SELF_ADDED, or BLIP_SUBMITTED (for >> simple example, see waveno...@appspot.com ) >> 3, observe logs ( >> https://appengine.google.com/logs?=&app_id=wavenotif&version_id=1b.337357556183848162&logs_form=1&severity_level=1# >> ) >> >> *Expected result*: Robot is notified for adding, and receives wave >> content. >> *Observed result*: No notification, or request from *WaveRobotGateway* * >> whatsoever* >> >> (this is a show-stopper bug, for most of my robots assume to be called for >> interaction) >> >> Looking forward to *any* solution, >> SDr >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-api@googlegroups.com To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
