Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.

RTM abnormal close 1006 - Messages not sent #463

Closed
rickul opened this issue Oct 27, 2016 · 1 comment
Closed

RTM abnormal close 1006 - Messages not sent #463

rickul opened this issue Oct 27, 2016 · 1 comment
Labels
bug Slack-related

Comments

@rickul
Copy link

rickul commented Oct 27, 2016 •
edited
Loading

Hi!
We have a problem with the RTM. When starting some conversations, the RTM connections is (always) lost with a 1006 abnormal close. This only happens in one specific channel, in others this never happens.
When it happens, RTM is reconnected automatically, but the messages are not being sent. I think, they should be sent after a reconnect. A comment in bot.send() in Slackbot_worker.js says:
/**

  • The RTM failed and for some reason it didn't get caught
  • elsewhere. This happens sometimes when the rtm has closed but
  • We are sending messages anyways.
  • Bot probably needs to reconnect!
    */
rickul added a commit to rickul/botkit that referenced this issue Nov 4, 2016
@rickul
force the bot sending messages through API; this commit closes issue h…
e06635e 
…owdyai#463
@rickul rickul mentioned this issue Nov 4, 2016
Closed
@peterswimm
Copy link
Contributor

Issue solved by #474

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Slack-related
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@peterswimm @rickul