Creating new persistent branch asks to upgrade even though my org is Pro

I have a Pro organization with 2 projects.
One project has got persistent branching enabled for one of the branches.

I want to enable persistent branching for the other project part of the same organization and it prompts me to upgrade even though I have Pro subscription already.

garyaustin•12/4/25, 9:10 PM

Is the project a micro project or still nano?

Nick GatzoulisOP•12/4/25, 9:17 PM

Looks like it's micro

Nick GatzoulisOP•12/4/25, 9:17 PM

Does it have to be nano?

garyaustin•12/4/25, 9:31 PM

No. I was thinking if it was Nano that might not meet whatever test they do for Pro and you would need to upgrade from nano to micro.

garyaustin•12/4/25, 9:32 PM

I've not seen any document saying only one project can do branches in an org, but don't know how common it is to try.

Nick GatzoulisOP•12/4/25, 9:33 PM

I'd assume each project in org has their own main production branch and you can create preview branches

Nick GatzoulisOP•12/4/25, 9:34 PM

the thing is, even if what they're asking is true (to upgrade), it's not possible, the upgrade button is greyed out, I'm already on Pro

Nick GatzoulisOP•12/4/25, 9:34 PM

Looks like a bug

garyaustin•12/4/25, 9:43 PM

Could be. I was in my initial comment assuming upgrade might also be from nano to micro as Pro defaults to nano for the first project if converted from Free.

Support is probably best bet.

Nick GatzoulisOP•12/4/25, 10:19 PM

I can confirm it's a UI bug

Nick GatzoulisOP•12/4/25, 10:19 PM

I just used the supabase CLI and I managed to make the branch persistent

garyaustin•12/4/25, 10:20 PM

Then might be better to file an issue in supabase/supabase github.

Creating new persistent branch asks to upgrade even though my org is Pro

Similar Threads

Similar Threads

Similar Threads