Docs
Troubleshooting
Common SupaClone clone failures, what they mean, and how to recover safely.
Last updated 2026-07-09
Target project is not empty
Use a fresh target project. If the target already has application schemas, objects, or Storage files, SupaClone may stop to avoid unsafe merging.
Fix:
- Create a new target project, or
- Delete/recreate the target resources after exporting anything important.
Permission denied
The database user or OAuth grant may not have enough permission for the selected clone scope.
Fix:
- Confirm the source connection can read the selected schemas.
- Confirm the target connection can create schemas, tables, policies, functions, and triggers.
- Reconnect Supabase if Management API scopes are missing.
Storage policy could not be created
Storage policies can depend on roles, helper functions, or target-specific assumptions.
Fix:
- Read the manual step in the clone report.
- Create the policy manually in the Supabase SQL editor.
- Verify public and authenticated access afterward.
Edge Function works but fails at runtime
The function code may have copied successfully, but secrets, callback URLs, or third-party services may still point at the wrong environment.
Fix:
- Re-enter missing secrets.
- Review webhook and callback URLs.
- Run a function smoke test against the target.
- Check target function logs.
Auth provider does not work
Auth provider secrets are not copied automatically, and OAuth providers often require environment-specific callback URLs.
Fix:
- Add provider secrets manually.
- Update redirect URLs in the provider dashboard.
- Confirm Supabase Auth site URL and allow list.
Data clone is slow
Large tables and Storage buckets take time and can be limited by network throughput, Supabase API behavior, or worker runtime.
Fix:
- Start with selected schemas or selected tables.
- Run structure-only first.
- Clone large Storage buckets separately when possible.
- Review the slowest table details in the report.
Report has manual steps
Manual steps are not necessarily failures. They usually mean SupaClone found a security-sensitive or platform-limited resource that should be reviewed by a human.
Complete the manual steps, then test the target environment before depending on it.
Ready to run a verified clone?
Start with a fresh target project, choose exactly what to copy, and review the clone report after the run completes.
Clone your first project free