Troubleshooting

Common problems and solutions.

Connection

"Failed to connect" during OAuth connection

Cause: The OAuth flow could not complete.

Solutions:

• Make sure you authorized access in the Supabase popup
• Try signing out of Supabase and then reconnecting
• If the issue persists, try using a Personal Access Token (PAT)

"Token expired" on the dashboard

Cause: The OAuth token has expired and automatic renewal failed.

Solutions:

• Click Reconnect next to the affected account
• If that does not work, disconnect and reconnect the account

My projects do not appear in the selector

Cause: The token does not have access to those projects, or they are in a different organization.

Solutions:

• Make sure you selected the correct connected account
• Verify that your Supabase account has access to those projects
• If the projects are on a different Supabase account, connect that account as well

Cloning

The clone is stuck at "Pending"

Cause: The worker could not pick up the job.

Solutions:

• Wait 1-2 minutes — there may be a startup delay
• If it persists beyond 5 minutes, cancel and re-run the clone

"Permission denied" during the clone

Cause: The token does not have sufficient permissions on the source or target project.

Solutions:

• Verify that you are an owner or administrator of both projects
• Reconnect your Supabase account to renew permissions
• With a PAT, verify that the token has the required scopes

"Extension not found" in the report

Cause: The source project uses a PostgreSQL extension that is not available on the target project's plan.

Solutions:

• Manually enable the extension on the target project (Supabase Dashboard > Database > Extensions)
• Verify that the target project is on a plan that supports the extension
• Re-run the clone after enabling it

Data is duplicated after a re-clone

Cause: Data cloning inserts rows without checking for duplicates.

Solutions:

• Clear the target tables before re-cloning data
• Use "Schema only" mode for structure updates
• Configure ignore rules for sensitive tables

The clone is very slow

Cause: Large tables, many files in storage, or slow connection.

Solutions:

• Set a row limit for data
• Exclude large tables via ignore rules
• Disable the Storage component if files are not needed

Verification

"Row count mismatch" in verification

Cause: Writes occurred on the source project during the clone.

Solutions:

• Discrepancies of a few percent are normal and expected
• For an exact copy, avoid writes to the source during the clone
• Re-run the clone if the discrepancy is significant

"Missing table" in verification

Cause: Table creation failed during the clone.

Solutions:

• Check the clone report for the exact error
• Verify extensions and permissions on the target project
• Re-run the clone

Scheduled Clones

My scheduled clone is not running

Possible cause:

• The schedule is disabled
• The connected account used has expired
• You have reached the Free plan limit

Solutions:

• Verify that the schedule is Enabled
• Reconnect the associated Supabase account
• Upgrade to the Pro plan if you have reached the limit

The schedule shows "Last run: failed"

Cause: The last scheduled clone failed.

Solutions:

• Click on the job to view the error report
• Fix the issue (permissions, extensions, etc.)
• The next clone will be attempted automatically at the scheduled interval

Billing

I can no longer run a clone — "Limit reached"

Cause: You have used your 3 free clones for the month.

Solutions:

• Upgrade to the Pro plan for unlimited clones
• Wait until the 1st of next month for the counter to reset