If you see a "Rate limit reached, waiting 30.0s" message while running the Slack Channel User Extractor Phantom, no action is needed, this isn't an error. It's a standard Slack API rate limit message. The Phantom pauses automatically for 30 seconds and then resumes on its own until all results are collected.
This is different from LinkedIn rate limiting. If you're seeing rate limit errors on LinkedIn Phantoms, see How to Handle Rate Limiting Errors.
Why you’re seeing this
This isn’t an error, it’s a standard Slack API limit message.
Slack restricts how many data requests (API calls) can be made in a short period. When this limit is reached, the Phantom temporarily pauses for 30 seconds before resuming automatically.
This delay can repeat if:
- The Phantom is processing a large Slack channel.
- Other apps or automations are using the same Slack account at the same time, increasing activity.
This behavior is set by Slack’s API and can’t be bypassed or customized.
What you can do
Let the Phantom finish running
This message is normal. The Phantom stays active and will automatically resume after each 30-second pause until all results are retrieved. Don't stop or relaunch the Phantom, let it complete on its own.
Use smaller channels when possible
Running the Phantom on smaller or less active channels reduces the number of API calls needed, which means fewer pauses. If you need to extract from a very large channel, expect multiple 30-second delays during the run.
Reduce competing API activity
If other Slack apps, integrations, or automations are running on the same account simultaneously, they share the same rate limit. Pausing other Slack automations during the Phantom run can reduce delays.
Frequently asked questions
Does the 30-second wait count against my execution time?
Yes. The Phantom stays active during the pause, so the 30-second waits are included in your total execution time. For very large channels with many pauses, this can add up.
Will the Phantom still collect all results?
Yes. The pauses don't cause any data loss. The Phantom resumes exactly where it left off after each 30-second wait and continues until all members are extracted.
Can I avoid the delay by using a different Slack account?
Potentially. Each Slack account has its own API rate limit. If the delays are caused by competing activity on the same account, using a different account with less activity could reduce pauses.
Does this affect other Phantoms running at the same time?
No. Slack's rate limit applies per Slack account, not across your PhantomBuster setup. Other Phantoms on different platforms (LinkedIn, Instagram, etc.) are unaffected.
How many times can the Phantom pause and resume?
There's no limit. The Phantom will pause and resume as many times as needed until it finishes processing the channel. Large channels with thousands of members may trigger dozens of pauses.
Is there a way to increase Slack's API rate limit?
No. The rate limit is set by Slack and applies to all users. There's no paid tier or setting to increase it.
If the error keeps showing up
If the Phantom stops entirely instead of pausing and resuming, or if it never completes the run after multiple pauses, get in touch with our Customer Care Team. Include:
- The Phantom name and link
- The Slack channel you're trying to extract from
- The launch log showing the pause messages
- Whether the Phantom completed or stopped mid-run