Issue with Viewing Group List in Slack Despite Granted Permissions: What to Do?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

Hello there, I have an issue with the sending a public message with slack - despite trying multiple times, I am unable to view the list of groups even though I have granted permissons.

What should be done?

Screenshot 2023-04-03 at 4.09.46 PM.png
Screenshot 2023-04-03 at 4.09.46 PM.png2364×1092 167 KB

2

I think this is a bug, opened here: [BUG] Slack with many channels hangs · Issue #5913 · PipedreamHQ/pipedream · GitHub

3

Hello , in order for me to reproduce you issue, may I ask are you a Slack workspace admin/owner? What permission do you have on your Slack workspace?

I’ve tested my account with Workspace owner permission and normal user and it seems okay (images below). Would you mind reconnecting your Slack account, allow Pipedream to connect with your Slack workspace (may need workspace admin permission) and try to select the channel again?

image.png
image.png1638×1774 291 KB

image.png
image.png1666×1788 301 KB

4

I’ve run into this as well, when listing channels for our corporate Slack workspace. is there anything we can do to make the async options for list Slack channels more performant?

5

By the way, why do we have the conversation and channelId props? Aren’t those the same thing?

6

I run into it frequently with our corporate workspace, almost never with this workspace. This one has many more users, the corp workspace has many more channels.

7

By the way, why do we have the conversation and channelId props? Aren’t those the same thing?
The channelId is used to fetch a private channel or a public channel. conversation includes private and public channels, direct messages and group direct messages

8

From what I’m seeing in the code,
These are the main execution steps the conversation prop’s async options go through that might slow things down:

  1. In the first page, it paginates through all the users in the workspace
  2. It fetches 200 conversations per page
    do you notice this happening when it tries to load the first page, second, or all subsequent calls too?
9

First page

10

Ok, let me edit the action and I’ll ask you to test it

11

Ah wait, nvm. The send-message-public-channel uses the channelId prop.

For each page:

  1. It fetches 200 channels
  2. Makes a call either to fetch information about a user or information about a channel.
    So for each page, it actually makes 1 call, then 200 calls, in parallel.

I’m checking the docs to see if these extra calls are necessary or not

12

OK can you please test the prop in the slack-conversation-prop-test branch?

13

Does it matter which action?

14

Not really I think, but please try with send-message-public-channel and send-custom-message

15

Initial tests — your version of public-channel action works better :pray::skin-tone-2:, registry and your version of custom-message action both working ok right now

16

Cool! I eliminated unnecessary calls for channels info, but users info calls are needed to get the username

17

Can you try and see with set-channel-topic?

18

It will list public and private channels

19

So far that is working well in my quick tests too

20

The worst case scenario is if the user has 200+ private messages with other users/groups.
Then it will lag when loading the prop.