Skip to content

Troubleshooting

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