Troubleshooting Guide

Common issues and solutions for DevSync.AI Dashboard.

Common Issues

500 Error When Creating Project

If you encounter a 500 Internal Server Error when trying to create a project:

  1. Check the browser console for detailed error messages
  2. Verify that database migrations have been run in Supabase SQL Editor
  3. Check that Row Level Security (RLS) policies are set up correctly
  4. Ensure the schema_type constraint matches your selection
  5. Review the error code and message in the console

Common causes: Missing database migrations, incorrect RLS policies, or constraint violations.

Migration Validation Fails

If migration validation fails:

  • Check SQL syntax for errors
  • Verify database connection string is correct
  • Review the validation error message for details
  • Test the SQL manually in your database client
  • Ensure database user has necessary permissions

Migration Execution Fails

If migration execution fails:

  • Check the error message in migration history
  • Verify database user has execute permissions
  • Check database connection string
  • Review SQL for syntax or logic errors
  • Ensure database is not locked or in maintenance mode

Can't See Scan Reports

If scan reports don't appear:

  • Verify project ID is correct in CLI scan command
  • Check that CLI sync was successful
  • Refresh the dashboard page
  • Verify API connection and authentication
  • Check browser console for API errors

Error Codes

Understanding error codes can help diagnose issues:

23514 - Check Constraint Violation

The value provided doesn't match a required constraint. Check that schema_type and other required fields match allowed values.

42501 - Insufficient Privilege (RLS)

Row Level Security policy prevents the operation. Verify RLS policies are configured correctly for your user.

23505 - Unique Violation

The value already exists (e.g., project slug). Use a unique name or slug.

23503 - Foreign Key Violation

Referenced record doesn't exist. Check that related records exist before creating dependent records.

Getting Help

If you're still experiencing issues:

  • Check the documentation for detailed guides
  • Review the troubleshooting guide for common solutions
  • Check browser console and network tabs for errors
  • Review migration history for execution errors
  • Contact support with error codes and messages

When reporting issues: Include error codes, messages from the console, and steps to reproduce the problem.

← Back to Documentation