Context:
In my Supabase environment, I have three types of branches: PRU, PRE, and Main (Default)
Schema:
PRU = Editor
PRE = Staging
Main = Production
The issue is that any changes I make in Supabase on the PRU or PRE branches are not reflected in WeWeb. Tables, actions, or anything else created on branches other than Main, which is intended solely for Production, are not reflected.
This is a major problem because making changes on the Main branch affects the project’s live data.
Could this be related to the integration?
Additionally, the branches frequently disconnect, resulting in an error stating that the connection to Supabase cannot be recognized, which disrupts workflows.
Same here, running into something similar to this too.
I’ve tried reconnecting the Supabase integration and recreating the affected table, both suggested in this thread: Integration issues with Supabase but neither fixed it for me. Not sure if that 500/“supabaseKey is required” issue was actually resolved yet or if this branch problem is separate.
My setup also has the Editor/Staging/Production branches not staying in sync with Supabase, and the connection drops randomly with an unrecognized connection error, similar to what’s described above. Would help to know if this is the same root cause or something new.
Workaround : First use the supabase plugin in the interface tab (not from the Data&API) to connect. Second Don’t use supabase branches, instead duplicate your supabase project and use the second project for editor/staging and use the first project for production.
Obviously any backend changes on supabase won’t ‘merge’ or sync on their own and will have to be manually replicated from your duplicate project to the original one.
@Ruak is right: it’s a known bug that the team is working on. It’s too early to give an ETA. We’re aiming for a first round of QA next week but the fix in production will depend a lot on how that goes and could still be a few weeks out.
Do you have any update on when this will be permanently fixed? We have been unable to work on our project using Supabase branches for weeks now.
A fix was supposedly deployed last week, but it only worked for a few minutes before crashing again. We have tried deleting the connection, removing the integration entirely, and reconnecting everything multiple times. However, the fix seems highly unstable, it works for a brief window and then stops functioning.
It is frustrating that a bug affecting paying users and potentially live production apps is not being resolved more quickly. We got a response from your support that the fix was delayed due to a backlog in validation from your team, which makes no sense for a critical issue like this.
I have already opened a support ticket, but I am not receiving the feedback or updates expected for an issue of this severity. I would appreciate a concrete update on the status of this fix as soon as possible.
I’m sorry I only saw the notification for this topic today. We released another fix related to this yesterday. Could you check if things are back to normal on your side?
If not, please send me a DM with the support ticket number and link to the editor so I can follow up on your project specifically.
