Most issues stem from Supabase configuration, GitHub OAuth setup, or free tier limits. Start with the relevant section below.
Authentication Issues
GitHub OAuth sign-in fails
- Verify GitHub OAuth is enabled in Supabase → Authentication → Providers → GitHub
- Check the OAuth callback URL matches:
https://your-project.supabase.co/auth/v1/callback - Confirm
.env.localhas correctVITE_SUPABASE_URLandVITE_SUPABASE_ANON_KEY
Session expires unexpectedly
- Check that your browser isn’t blocking third-party cookies
- Clear local storage for the playground domain and sign in again
Organization memberships not syncing
- Ensure the OAuth app requests the
read:orgscope - Verify your GitHub org allows OAuth app access
- Sign out and sign back in to force a sync
Supabase Connection Issues
”Failed to connect to Supabase”
- Check if your Supabase project is paused (free tier pauses after 7 days of inactivity)
- Verify environment variables are correct
- Test directly:
curl https://your-project.supabase.co/rest/v1/ -H "apikey: your-anon-key"
Preventing project pausing
Set up a GitHub Actions cron job to ping your project every 3 days:Row Level Security (RLS) Errors
”new row violates row-level security policy”
- Verify you’re authenticated — sign out and sign back in
- Check your workspace membership and role in Supabase →
workspace_memberstable - Viewers cannot create/edit policies; Editors can create/edit but not manage members
”permission denied for table”
- Ensure RLS is enabled on all tables
- The
audit_logtable is append-only — update/delete operations are blocked by design
Policy Editor Issues
Monaco Editor not loading
- Hard refresh:
Ctrl+Shift+R/Cmd+Shift+R - Check browser console for JavaScript errors (Monaco requires WebAssembly)
- Ensure browser is up to date (Chrome 90+, Firefox 90+, Safari 15+)
- Disable content-modifying browser extensions
”Policy name already exists”
Policy names must be unique within a workspace. Choose a different name or open the existing policy from the registry.Governance Workflow Issues
Can’t edit an Approved/Production policy
This is expected. Create a new version via “Create New Version” and submit through the approval workflow.Emergency bypass not available
- Must be enabled in Workspace Settings → Governance
- Only workspace Owners can perform emergency bypasses
Free Tier Limitations
Supabase
Vercel
GitHub Actions
The playground displays usage warnings at 80% and 95% thresholds.
Error Message Reference
Support Resources
- Getting Started — Initial setup
- Governance Workflow — Approval processes
- Compliance Mapping — Framework mapping
- Audit Trail — Logging and export
- CI/CD Integration — GitHub Actions workflows
- RBAC Simulator — Role-based testing
- Policy Templates — Template documentation
- Supabase Documentation
- Vercel Documentation
- GitHub Actions Documentation

