Verifying a Clone

After a clone, you can run a verification to confirm that the target project matches the source project.

Why Verify?

A clone can have minor discrepancies:

• Writes to the source project during cloning
• Components that failed silently
• Differences in versions or extensions

Verification gives you a clear view of the actual state.

Running a Verification

1. Go to Dashboard > Clones > [your clone] > Results
2. Click Verify
3. The verification runs (typically 10 to 30 seconds)
4. The report appears

What Is Verified

Schema

• Do the source tables exist in the target?
• Do the columns match (name, type, nullable, default)?
• Are the constraints identical (PK, FK, unique, check)?
• Are the indexes present?

Data

• The row count per table is compared between source and target
• Significant discrepancies are flagged

Missing Objects

• Functions, views, or triggers present in the source but missing from the target
• RLS policies that were not applied

Verification Results

Interpreting the Results

Small Row Differences

Differences of a few percent are normal if the source project receives writes during the clone. This is not a problem.

Missing Tables

If a source table does not exist in the target, it means the creation failed during the clone. Check the clone report for the error.

Missing Columns

If a table exists on both sides but columns are missing in the target, you can re-run a clone — the missing columns will be added automatically.

What to Do If Verification Fails?

1. Review the report to identify the discrepancies
2. Re-run a clone — the process is designed to be idempotent
3. If the problem persists, check the extensions and permissions on the target project
4. You can also restore from a backup if you have one

Next Steps

• Restoring a Backup — In case of issues
• Components — Details on what is verified