-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[Slack] A rate-limit has been reached #14113
Comments
Thank you for opening this issue! 🔔 @momme-rtf @Elliot67 @jfkisafk @thomaslombart @RobErskine you might want to have a look. 💡 Author and Contributors commandsThe author and contributors of
|
Are you getting this consistently, or does the error go away after a few seconds or minutes? If the latter happens, it's normal behavior. |
Always |
Could you share a recording? It'll make it easier to see what's happening. |
Sure. Screen.Recording.2024-08-21.at.10.53.21.mov |
@thomaslombart When I try to select |
@obaidch24 Are you in a very large Slack workspace ? How many users and public channels are in it ? Rate limiting might be the alternative ending to #13067 . We can retrieve 1_000 users per requests and 1_000 conversations which means rate limiting could start to appear on workspace with more than ~15k users. Simplest solution is to fetch and cache all the data bit by bit, preferably in the background if raycast allows it. |
Yes, the workspace is quite large. I'm not sure how many users and public channels it has. I guess it should have more than 4K active users. |
It could indeed be due to the large workspace. @obaidch24, if you have other Slack workspaces, could you test the extension in a smaller one and let me know if it works? |
Unfortunately, I don't have another one. |
This issue has been automatically marked as stale because it did not have any recent activity. It will be closed if no further activity occurs in the next 10 days to keep our backlog clean 😊 |
@Elliot67 @thomaslombart Will this issue be addressed? |
I'm fully-focused on another project, so I won't have much bandwidth for that. Please feel free to submit a PR, and I'll review it 🙂 |
Is there a way to just get and build the slack extension locally and submit the changes? I have a sample slack app, where I have this code to handle the same issue. |
Here's our guide about contributing to extensions: Contribute to an extension |
I debugged it a bit. - slackWebClient = new WebClient(token, { rejectRateLimitedCalls: true });
+ slackWebClient = new WebClient(token, { retryConfig: retryPolicies.fiveRetriesInFiveMinutes }); The problem is I have over 18k channels/conversations. And the method Error: Worker terminated due to reaching memory limit: JS heap out of memory We can do following re-factoring to fix these issue
|
I have made the change and it should work in most of the cases. npx @raycast/api@latest publish I am running into following
@thomaslombart Do I need to upgrade my account or is there a workaround ? |
I'm just starting out with Raycast and got my org to approve this extension in Slack, but I'm hitting the exact same problems described here. Are there any further developments to allow users in large Slack organizations to use the extension? |
@jhasubhash I'll take a look at your error and get back to you on that 🙂 |
@jhasubhash are you trying to our public store or some private store? The free plan allows you to have up to 5 commands in a private store - after that, you need to upgrade your organization to a paid plan, you can read more about it on our pricing page: https://www.raycast.com/pricing However, if you see this message while trying to participate in our public store, it means there's a bug in our publishing code that we need to check. |
Extension
https://raycast.com/mommertf/slack
Raycast Version
1.81.2
macOS Version
14.6.1
Description
Error:
Steps To Reproduce
Current Behaviour
No response
Expected Behaviour
No response
The text was updated successfully, but these errors were encountered: