No Data Returned
Fix alice skills that run successfully but return empty or unexpected results
No Data Returned
What You See
You run a command like /alice signups --days=7 and alice responds with a valid message, but the results table is empty or shows "No results found."
Quick Fix
Widen the time period. If the skill uses a date filter, try a much wider range to confirm data exists:
/alice signups --days=365If this returns results, the issue is that your original time period had no matching data.
Detailed Diagnosis
1. Check the Source Data Directly
Verify the data you expect actually exists:
- Stripe -- Open your Stripe Dashboard and confirm the customers, subscriptions, or charges you expect are present
- Supabase -- Open the Supabase Dashboard Table Editor and check that the table has rows matching your filters
2. Review Parameter Defaults
Every skill parameter has a default value. If you are not passing a parameter, the default may be filtering too aggressively.
Run the help command to see defaults:
/alice signups --helpThis shows each parameter with its type and default value. A --days=7 default means the skill only looks at the last week by default.
3. Check Filter Conditions
If you built the skill with the Visual Builder or Raw SQL, the filters may be too restrictive:
- Go to Dashboard > Skills and click on the skill
- Click Edit to open the skill builder
- Review the Query step -- check each filter condition
- Use the Test panel to run the query with different parameter values
4. Verify RLS Policies (Supabase Only)
If your Supabase project has Row Level Security enabled, alice's service role connection may not have access to all rows.
- Check the RLS policies on the table your skill queries
- alice uses the credentials stored during source connection -- if you connected with a specific API key, RLS policies apply to that key's role
- Temporarily broaden the RLS policy or use the service role key during testing
5. Combined Query Join Mismatch
For combined queries that join data across Stripe and Supabase:
- The join key must match exactly across both sources (e.g., email addresses must be identical, including case)
- If the join returns empty, test each source query independently to confirm both return data
- Check that the join key field exists in both query results
6. Stripe Test Mode vs Live Mode
If your Stripe account is in test mode, alice will only return test data. Make sure:
- You connected the correct Stripe account (live vs test)
- The queries are looking at the mode where your data exists
Common Causes by Skill Type
| Skill | Common Empty Result Cause |
|---|---|
mrr | No active subscriptions in the connected Stripe account |
signups | Date filter excludes recent signups (check timezone) |
churn-risk | No customers match all three risk criteria simultaneously |
failed-payments | No payment failures in the time period (that is good news!) |
active-users | Supabase last_sign_in_at column missing or null for all users |
Still Stuck?
Email support@alicehasnoidea.com with the skill name, the command you ran (including parameters), and a screenshot of the skill builder's Test panel results.
Was this page helpful?