> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocket.new/llms.txt
> Use this file to discover all available pages before exploring further.
# Push migration scripts
> Apply Rocket.new-generated SQL migration scripts to keep your Supabase schema in sync.
export const LlmsDirective = () =>
For the complete documentation index, see llms.txt.
For a lightweight markdown version of this page, append .md to the URL.
;
Whenever your app creates or updates tables, Rocket generates a Supabase migration script. This guide covers reviewing and pushing those scripts, avoiding issues from skipped changes, and troubleshooting common errors.
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.
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."
To fix this:
Go to [supabase.com](https://supabase.com) and open the paused project.
Click **Restore Project** to reactivate it.
Return to Rocket and push the script again.
### 2. Supabase project was deleted or disconnected
What you will see:
"Your connected Supabase project appears to be deleted."
To fix this:
In Rocket, go to **Connectors → Supabase**.
Select a valid project from the dropdown.
Click **Save**, then try pushing the script again.
### 3. Supabase is temporarily down
What you will see:
"Your Supabase project 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.
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.
If it is still visible, click the script name to preview it, then copy the SQL.
**OR**
In Rocket, open **Code**, then open the `supabase/migrations/` folder. Each script is saved there with a name and timestamp. Copy the SQL from the script you want.
Paste the SQL into the SQL editor in your Supabase dashboard and click **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.
Every Rocket script keeps your app on track. Push as they appear to stay aligned and avoid surprises.
***
## What's next?
Add backend logic deployed directly from chat.
See all Supabase features available in Rocket.