Supabase plugin not listing all tables after recent WeWeb update

[rebeferrer (Rebeca Ferrer)]

Hi everyone,

Since the WeWeb update last week, several of my Supabase collections have stopped working with a PGRST205 error. I’m using the old Supabase + Supabase Auth plugins (not the new Data & API integration).

The problem:

The Supabase plugin in WeWeb only lists 5 tables in the realtime collections section: centros, categorias_usuarios, roles_profesionales, herramientas, herramientas_centros. But my Supabase project has many more tables — banners, perfiles, roles, users_roles, delegaciones_asisa, etc.

Any collection pointing to a table not in that list of 5 returns this error when fetching: PGRST205: Could not find the table 'public.X' in the schema cache

Interestingly, some of the missing ones are actually views (not tables), like herramientas_usuario and provincias_centros — marked as UNRESTRICTED in Supabase. Not sure if that’s related.

What I have already tried:

• Running NOTIFY pgrst, 'reload schema'; in Supabase SQL Editor → Success, no change

• Clicking refresh in the Supabase plugin realtime collections section → only the same 5 tables appear

• Clicking refresh in the Supabase Auth plugin roles table dropdowns → same issue, values not found

Important: Supabase Data & API integration is NOT connected — no duplicate connection conflict.

All affected tables have RLS enabled with policies for authenticated role. The tables that do work are also RLS-enabled, so I don’t think that’s the differentiator.

Has anyone else seen this after the update? Is there a known fix?

Thanks

[rebeferrer (Rebeca Ferrer)]

Update: we recently upgraded to the Scale plan and a team member connected both the Interface Repository and Server Repository to GitHub as part of the onboarding. This coincides exactly with when the problems started. Could connecting the Server Repository have caused a conflict with the existing Supabase and Supabase Auth plugins?

[rebeferrer (Rebeca Ferrer)]

Update — Problem solved:

Found the root cause. We had created 3 branches in Supabase (production, staging, and a test branch). WeWeb was pointing to the test branch (“Pru”) instead of “main”. That branch didn’t have the latest table updates, which is why WeWeb couldn’t find those tables in the schema cache — they simply didn’t exist in that branch.

Switching WeWeb back to the correct Supabase branch (main) resolved all the PGRST205 errors immediately.

If anyone hits a similar issue, check which Supabase branch your WeWeb plugin is pointing to — it’s easy to miss!

[Joyce]

Ah, perfect! I was just about to look into this. Thanks so much for taking the time to update us on here, really appreciate it