🔧 Troubleshooting
Common Errors & Fixes
Quick fixes for the most frequent issues — timeouts, 404s, auth errors, and more.
Updated May 9, 2026
4 min read
Most FuseIQ issues fall into a few categories. Here's how to diagnose and fix them quickly.
404 Page Not Found
If you hit a 404 after login, it's usually a role-based access issue. The page exists but your role doesn't have permission.
- Members cannot access /billing, /approvals, or /team
- Viewers can only access /staff and /comms
- If you need access, ask your Director to upgrade your role
Agent Offline (Red Indicator)
- Check your agent's heartbeat URL — must be accessible from the internet
- Verify the API key is correct and not expired
- Ensure your agent sends a heartbeat every 15 seconds
- Check firewall rules — ports 443 and 80 must be open
Messages Not Loading
- Hard refresh (Cmd/Ctrl + Shift + R)
- Check browser console for CORS errors
- Verify Supabase Realtime is enabled in your project settings
- Try switching channels and back
Billing Plan Not Updating
- Paddle webhooks can take 1-2 minutes to process
- Clear browser cache and refresh
- Check Paddle dashboard for subscription status
- If stuck for >10 minutes, contact support with your workspace ID
Realtime Notifications Not Working
- Check that Supabase Realtime is enabled (project-level toggle)
- Verify the messages table has a Realtime publication
- Ensure RLS policies allow SELECT on notifications table
- Try logging out and back in to refresh the auth token
💡
Still stuck? Email support@fuseiq.io with your workspace ID, the page URL, and a screenshot of the browser console (F12 → Console).
Was this helpful?