Lovable Supabase connection broke: 'Supabase connection issue'

What it means in plain English

This page is for a Lovable project connected to your own Supabase project, not Lovable's built-in backend. Lovable's Supabase guide lists this exact message: when the Supabase view shows Supabase connection issue, "Lovable can't find the connected Supabase project. The linked project may have been deleted in the Supabase dashboard, or your workspace's access to the Supabase organization may have changed."

The connection has two levels. The project connection says which Supabase project this Lovable project uses. The workspace's linked organizations say which Supabase organizations the whole workspace can use. Either one can break.

Likely causes

• The Supabase project was deleted in the Supabase dashboard.
• The workspace's access to the Supabase organization changed or expired. Lovable's Connectors page has an option to "reconnect one whose access has expired."
• The Supabase project is paused or still provisioning. Lovable says those projects "can't be connected" and shows Check project status in Supabase.
• A publish failed with an external connection message. Lovable's publish guide gives "an expired Supabase connection" as an example.
• You aren't a workspace owner or admin, so Add Organization is disabled.

How to fix it, step by step

1. In the editor, open More → Supabase. Lovable says this view shows "the connected project's name and health status."
2. Open the Supabase dashboard and check that the project still exists and is active. If it is paused, make it active first, then come back to Lovable.
3. To restore access, open Connectors from the dashboard sidebar, select Supabase, and use Manage Connected Organizations to reconnect the organization. The Manage organizations button in the project's Supabase view opens the same place.
4. If the project was deleted or you want a different one, click Disconnect in More → Supabase, confirm, then connect again and pick the project. Lovable says disconnecting "does not change your code and does not delete anything in your Supabase project."
5. If Add Organization is disabled, ask a workspace owner or admin to link the organization. Lovable says that after it is linked, "anyone with edit access to a project can connect it."
6. If the connect link says Wait for Lovable to finish working, let the current chat request or operation finish, then start the connection again.
7. If publishing failed because of the connection, fix the connection first, then click Try again in the Publish dialog.

How to check it worked

• More → Supabase shows the connected project's name and health status, with no connection issue.
• The app reads and writes data again, and publishing works. If publishing still fails, see Lovable app not deploying.

Sharing one Supabase project between several Lovable projects is allowed, but Lovable warns that they "read and write the same data and overwrite each other's secrets, including LOVABLE_API_KEY."

Questions people ask

Does disconnecting Supabase from Lovable delete my data?

No. Lovable says disconnecting stops it from deploying edge functions and reading your database schema, but it does not change your code or delete anything in your Supabase project.

Why can't I click Connect next to my Supabase project?

Lovable says projects that are paused or still provisioning in Supabase can't be connected, and it shows Check project status in Supabase. Make sure the project is active in the Supabase dashboard, then try again.

Who can reconnect the Supabase organization in Lovable?

Workspace owners and admins link and reconnect Supabase organizations. After an organization is linked, anyone with edit access to a project can connect it to a Supabase project from that organization.

Sources

• https://docs.lovable.dev/integrations/supabase (opens in a new tab)
• https://docs.lovable.dev/features/publish (opens in a new tab)