Slack Not Responding
Fix alice slash commands that time out, show errors, or do not respond in Slack
Slack Not Responding
What You See
You type /alice mrr (or any command) in Slack and one of the following happens:
- Nothing at all -- no response, no loading indicator
- Slack shows "This slash command experienced an error"
- The loading indicator appears but never resolves
- You get "dispatch_failed" or "command_not_found" errors
Quick Fix
Reinstall the Slack bot. Go to app.alicehasnoidea.com, navigate to Settings > Workspace, and click Reconnect Slack. This refreshes the OAuth tokens and re-registers the slash command.
Detailed Diagnosis
If the quick fix did not work, walk through these checks:
1. Bot Not Installed
The most common cause. The Slack bot installation is separate from your Slack login.
- Go to Dashboard > Settings > Workspace
- Check if the Slack Bot Status shows Connected (green)
- If it shows Disconnected or Not Installed, click Add to Slack to install
Your Slack workspace admin may need to approve the installation if your workspace restricts app installs.
2. No Sources Connected
Skills query data from connected sources. If no sources are connected, commands will fail.
- Go to Dashboard > Sources
- Verify at least one source (Stripe or Supabase) shows Connected
- If none are connected, follow Connect Stripe or Connect Supabase
3. Skill Does Not Exist
You may be trying to run a skill that has not been created yet.
- Run
/alice helpin Slack to see all available skills - If the skill is not listed, create it from Dashboard > Skills > New Skill
- Check for typos in the slug (e.g.,
/alice mrrvs/alice MRR-- slugs are case-sensitive)
4. OAuth Token Expired
Slack OAuth tokens can expire if your workspace admin rotates tokens or if alice's app was reinstalled.
- Go to Settings > Workspace and check the last connection timestamp
- Click Reconnect Slack to refresh the token
- If you are a workspace admin, check Slack Admin > Manage Apps > alice to verify the app is still approved
5. Rate Limited
If you have been running many commands in a short period, you may have hit the rate limit.
- The default limit is 30 skill executions per hour
- Wait a few minutes and try again
- Check Dashboard > Logs to see if recent executions show a
rate_limitedstatus
6. Source Credentials Expired
If the underlying Stripe or Supabase OAuth token has expired:
- Go to Dashboard > Sources
- Check if any source shows Error or Expired status
- Click Reconnect to re-authorize
Error Codes
| Error | Meaning | Fix |
|---|---|---|
SLACK_NOT_INSTALLED | Bot not in workspace | Install from Settings > Workspace |
NO_SOURCES | No data sources connected | Connect a source |
SKILL_NOT_FOUND | Unknown command slug | Check /alice help for available skills |
SOURCE_AUTH_EXPIRED | OAuth token expired | Reconnect the source |
RATE_LIMITED | Too many requests | Wait and retry |
EXECUTION_TIMEOUT | Query took too long | Simplify the query or add filters |
Still Stuck?
Email support@alicehasnoidea.com with the exact error message and the command you ran. Include a screenshot of Dashboard > Logs if possible.
Was this page helpful?