Random behaviour to join a second time a nodejs user.

Beantwortet

Folgen

Alejandro

• 8. Juni 2018 13:00

Good afternoon,

scenario :

User A (WEB), invite User B(Web), invite C(nodejs) . Both are introduced directly in the bubble.

User C check  rainbow_onbubbleinvitationreceived event, and event is recieved :

2018-6-8 14:40:15 [1528461615478] - debug: SDK - New Bubble recieved 5b1a792f55dee87f6bf779db

but it doesn't receive any IM message. If User C is restarted then start to receive IM again.

It's random. Sometimes user C can receive IM from beginning, and other times it's needed to restart bot.

NodeJS (1.41.4).

It's using sandbox envirionment.

0

• 

  Pascal BORSCHNECK

  • 11. Juni 2018 07:04

  Hi Alejandro,

  Do you know HOW much Bubble your user C has ?
  I'll have to check but if I remember right, there is a limitation for number of "active" bubble, 300, see doc

  https://hub.openrainbow.com/#/documentation/doc/sdk/node/guides/Managing_bubble

  Extract:

  Any Rainbow user from any profile can join a maximum number of 300 Bubbles at a time. If the user has more than 300 Bubbles, the remaining Bubbles will be considered as inactive and so the user will not be notified from incoming messages received in these Bubbles. To limit the number of active Bubbles, they can be leaved or closed if no more used.

  Best regards,
  Pascal

  0

  Aktionen für Kommentare Permalink
• 

  Pascal BORSCHNECK

  • 21. Juni 2018 09:06

  Hi, this issue is solved into the new 1.41.5 release.

  0

  Aktionen für Kommentare Permalink

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.