Skip to content
- Verify the bot is a member of the target channel: open the channel and type
/invite @FluidRAG
- Confirm
channels:read and groups:read scopes are assigned to the bot token
- Reinstall the app to workspace after adding new scopes
- Check the Health page in Admin UI for connection status
- Verify the user token (
xoxp-) is configured — without it, only client-side scanning is available
- Confirm
search:read scope is assigned to the user token
- Try a broader query — the search uses keyword matching in fallback mode
- Check that the bot is a member of channels containing the messages you’re searching for
- Try extending the time window (e.g., “in the last 30 days”)
- Verify Slack is enabled on the Connectors page in Admin UI
- Check that at least one channel is selected for extraction
- Confirm RQ workers are running:
docker-compose ps rq-worker-1
- Check the RQ Dashboard at
http://localhost:9181 for failed jobs
- Try triggering extraction manually via the Sync Now button on the Slack connector card
- Check the RQ Dashboard for jobs stuck in retry loops
- Reduce the number of channels selected for extraction
- Increase the extraction schedule interval (e.g.,
0 */12 * * * for every 12 hours)
- Verify your Slack plan’s API rate limits at api.slack.com/docs/rate-limits
- Verify the Slack connector is enabled on the Connectors page in Admin UI
- Confirm
SLACK_BOT_TOKEN is set (check the connector’s Credentials tab)
- Try the manual override: prefix your query with
/slack
- Check server logs for authentication errors