-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Team support ? #39
Comments
Hello, did you ever find a solution for this issue? I ran into the same problem. The only workaround I can come up with is to create a separate bot user for each team, and just run two separate instances of mattermost_bot. That seems ugly. |
The issue is the server returns error 500 with the message: There is no channel with channel_id=ojdoaz586381udmyxoaadhcs1w on team with team_id=n7or4d5km3r7mqez11hqcr7wiw My guess is the bot code would need to be refactored to comprehend dealing with multiple teams. |
@gotlium Hello, did you ever find a solution for this issue? I ran into the same problem. The only workaround I can come up with is to create a separate bot user for each team, and just run two separate instances of mattermost_bot. That seems ugly. |
Hi,
it seems mattermost_bot doesn't like when poeple speak to him from different team? Does mattermost_bot support this ?
Here is the traceback when sending msg to the bot from another team. The bot account is part of this other team.
Thanks for any help
The text was updated successfully, but these errors were encountered: