Hey guys, wanted to bring up 2 things 1. not sure if this is even a misunderstanding from my end, but I've setup the triggers in a slack workspace (SLACKBOT_CHANNEL_MESSAGE_RECEIVED) and now I'm getting messages from channels where the bot is not present, not even I am in some of those channels, I thought that triggers will be fired only in channels where the bot is present, I'm I missing something? I'm aware that there is a channel_id config prop, it is not present in my setup, but still, it should listen only the channels where the bot is present, shouldn't it? 2. Probably this is not an issue (I think), would like to have some help here if possible, but when trying to setup triggers in my local env, it works, but when trying to do it in a different env using the same code, just different auth configs it just does not work, I checked the scopes that we're using in the local oauth app and in the other that it's failing and we're using the same scopes, this is the error I got

Error: 400 {"error":{"message":"Invalid webhook configuration for trigger \"SLACKBOT_MESSAGE_REACTION_ADDED\": Failed to get team info: {'ok': False, 'error': 'missing_scope', 'needed': 'team:read', 'provided': 'identify,channels:history,groups:history,im:history,mpim:history,channels:read,groups:read,im:read,mpim:read,search:read,users:read,users:read.email,search:read.public'}","code":1212,"slug":"TriggerInstance_WebhookConfigInvalid","status":400,"request_id":"e81b6b79-9654-4aeb-b45e-827a92d5e2e7","suggested_fix":"Verify the trigger configuration is valid and the connected account has the required permissions. Check the error details above."}}

I've already checked the keys and the scopes available in that scope as in the images attached. https://cdn.discordapp.com/attachments/1503488715870179348/1503488716121833593/image.png?ex=6a03887b&is=6a0236fb&hm=82a872716af9486da362c2866bf80d84091abb138c76ca53827ff47eb8f81ee2& https://cdn.discordapp.com/attachments/1503488715870179348/1503488716642189342/image.png?ex=6a03887b&is=6a0236fb&hm=ff33b24a10cb6cc2ea280c6abf4f19f4ca7c2f9d7660cabd9e2fdcffd66fae39&

hi @Mr. Roiz, we are checking this.

@Uday any update for this?

Hi @Mr. Roiz, sorry for the dealy. We've confirmed a bug with our Slack trigger and I've escalated it to our team! Also, for reference, could you share the connected accountID you are using to create a trigger? It'll help us in analysis and if we require deeper debugging. Thanks for understanding : )

hey, sure, this is one of the connected accounts that I'm using ca_AocuOVWDOm8l