Skip to main content
Keep your Supabase schema in sync. This guide covers reviewing and pushing Supabase scripts as they appear, avoiding issues from skipped schema changes, and troubleshooting common push errors.You need:
  • A Supabase project connected to your Rocket app

Not connected yet? Follow the steps in our Supabase Integration Guide.

​
When Rocket generates a script

Whenever your app creates or updates tables, Rocket automatically generates a Supabase script. It appears in the chat window with a preview and two options: push or discard.
Popup showing a generated Supabase script with options to preview, push, or discard.Popup showing a generated Supabase script with options to preview, push, or discard.
Each script popup includes:
  • A clickable script name to preview the schema.
  • A Push to Supabase button to apply the changes.
  • A Discard button to skip the script.

​
What happens if you skip it

If you ignore the popup, the changes will not apply to Supabase.
Skipping scripts can break your app. Later scripts may also fail if earlier fields or tables are missing.
Rocket does not automatically retry or reapply missed scripts. Push them as they appear to keep your schema in sync.
Each script depends on previous changes. Push them in order to avoid conflicts.

​
Troubleshooting push errors

If a script fails to push, here is how to identify and resolve common issues.

​
1. Supabase project is paused

What you will see: “Your Supabase project is currently paused.”
Error message indicating the connected Supabase project is paused.Error message indicating the connected Supabase project is paused.
To fix this:
  1. Open your Supabase dashboard.
  2. Click Restore Project to reactivate it.
  3. Return to Rocket and push the script again.
Restore Project button highlighted in the Supabase dashboard.Restore Project button highlighted in the Supabase dashboard.

​
2. Supabase project was deleted or disconnected

What you will see: “Your connected Supabase project appears to be deleted.”
Error message indicating the Supabase project is deleted or disconnected.Error message indicating the Supabase project is deleted or disconnected.
To fix this:
  1. In Rocket, go to Integrations → Supabase.
  2. Select a valid project from the dropdown.
  3. Click Save, then try pushing the script again.
Rocket Integrations screen with Supabase project reselected.Rocket Integrations screen with Supabase project reselected.

​
3. Supabase is temporarily down

What you will see: “Your Supabase project is temporarily unavailable.”
Message showing Supabase is temporarily unavailable.Message showing Supabase is temporarily unavailable.
Wait a few minutes, then try pushing the script again.

​
4. The script has a schema error

What you will see: An error message and a Fix it button.
Fix it button displayed in the schema error message.Fix it button displayed in the schema error message.
Click Fix it. Rocket will automatically repair the script and generate a corrected version.
Rocket handles most schema issues, including naming conflicts, missing dependencies, and broken triggers.

​
Manually running a script

If you discarded a script and later want to apply it, you can run it manually in Supabase.
  1. From the script popup: If it is still visible, click the script name to preview it, then copy the SQL.
Preview popup of a discarded script with copy option.Preview popup of a discarded script with copy option.

OR
  1. From code view: In Rocket, go to code view, then open the supabase/migrations/ folder. Each script is saved there with a name and timestamp. Copy the SQL from the script you want.
Rocket code view showing the Supabase migrations folder.Rocket code view showing the Supabase migrations folder.
  1. Paste the SQL into the SQL editor in your Supabase dashboard and click Run.
Supabase SQL editor showing a pasted migration script ready to run.Supabase SQL editor showing a pasted migration script ready to run.
If you change your connected Supabase project, you must run all scripts from the supabase/migrations/ folder in sequence to match your app’s schema.

Schema synced, app ready.

Every Rocket script keeps your app on track. Push as they appear to stay aligned and avoid surprises.