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.