GaryAustin1

How did you clear the storage? You have to always have used the UI or API to delete files and never delete rows from storage.objects with SQL. Also I believe the indicator is an average for the period and goes down slowly each day if you reduced the size.

You could try a restart (which restarts auth on your instance), but upgrade probably did that. So in the dashboard UI it shows auth health as bad? Any errors in the Auth or Postgres logs?

If you deleted the entire project then they (Supabase support) have said many times it can't be recovered. If just the database then you can go to Pro and everyone says there are daily backups there.

You need to ask support. The informal path I have to an employee has been responded to twice saying you have been given info.

Not sure what is being "asked" here. You don't understand the warning/event? You can't reduce your storage size? You think the message is in error?

(Edit) You could have Nano in a Pro org, but that still costs $10 a month so no reason to. You would move them in from a Free org for instance. Free projects are only the two you get from Free orgs.

I bumped again to my Informal path. Any chance this project/org was created with V0/Bolt/Lovable? They won't have a Supabase dashboard.

Support/Supabase will not likely see your info here. I passed on your ticket # and the 1 employee that checks for tickets needing to be looked at marked that he did what ever he does earlier today. He is not part of support and just helps out INFORMALLY by making sure tickets are not lost. You need to resolve this thru support and it sounds like you are in touch with them.

This covers a few things: https://supabase.com/docs/guides/platform/database-size Tables with lots of deletes/updates will take up lots of space beyond the visible rows until vacuumed. I assume you sent this to support also as you don't present any project info which no one in Github/Discord could use anyway.

Do you disk I/O charts in Observability Database section show continued high use? If not for most this seems to go away after 24 hours. Disk I/O burst budge builds back up hourly over a 24 hours period if not used.

Drop your ticket # here I can try and get it bumped with an informal path thru an employee in Discord.

I bumped your ticket # to an Informal path we have in Discord, but that is monitored by 1 employee and it is the weekend.

DId you try a restart of the instance? There have been no reported outages. Support may be needed for this and you should file a ticket if you have not.

What is your exact situation? Do you have projects locked up in pausing process like the OP? Do you have team members in your ORG that have a total of more than 2 free projects?

I don't think they (supabase) will need anything else you should get a 2nd email when it moves to the infra team to actually fix.

Only support can resolve this. If you drop your ticket # here we have an informal way in Discord to bump tickets thru one employee.

What is your USING Policy for Select? You have to meet that.

You can drop your ticket # here and we have an informal way to bump them in discord to an employee.

The new asymmetric jwt's will not work with jwt checking enabled. Also the new publishable and secret keys will not work with it. https://supabase.com/docs/guides/functions/auth

Support is the only way. How did you project get paused? I will bump this in an Informal queue we have in Discord that an employee monitors.

Sorry no. You are in time order with Pro plans in that queue for similar down issues and it is still the weekend which is slower. It varies a lot from what I've seen.

You are Pro and have a ticket in and support will have to fix it. You could take the backup to another instance but that involves set up and changes to your app. Have you received email it is moved to infra yet? That is the next step.

If you are not getting an error then typically this means you have RLS enabled and don't meet RLS for the select policy. Next.js also does caching in many cases which can make it hard to test if you change things on the server after it has cached. If you find you have an RLS problem and fix it you may need to figure out next.js caching or change the query filter so it does not get cached in order to test.

Probably not, but don't see it hang in storage like this typically (versus all fail). I'll add your ticket #'s to the informal queue we have in discord.

Can you restart from general settings?

If you have feedback for Supabase on this then either supabase/supabase issues for docs or supabase/cli github as related to the CLI.

Sorry, I don't use the CLI so can't comment on that. But If your data is gone, all you can do is get a back up. If there is something unclear with the CLI process then generate an issue in supabase/cli or leave comment here, but these are not normally monitored by Supabase staff.

I see a bit of info there is supposed to be a warning about it removing data. If I read this correctly it does a db-reset. https://github.com/supabase/cli/pull/3635 But I don't use migrations so could be wrong. If you don't have a backup then only way would be to go to Pro for min one month and get the last daily backup which even though not documented every user that has done it says they are there.

You did not drop your ticket # . I have no guesses as to why that would happen as pausing does not delete projects and Supabase does not either. Did you have any team members on your account? You could also try the dashboard from another device, but doubt that will matter.

You need to find the account that has them. Do you have emails sent when they were paused? Did you use Github to signup? You can drop your ticket # here and I have an informal path to try and bump it for situations where it has been awhile. Nothing you can do directly.

If not in use your projects are paused, not deleted even after many months. Are you sure you did not create the projects with Lovable/Bolt/Vercel or similar? If so they would not appear in a Supabase dashboard. Contacting support would be the only way to get someone to look at your account.

Yes the trigger function by default will run as authenticated role if that is the user role that did the update. If done from SQL then you might want to add code to check for Postgres role if you want that to update those columns. Trigger would only be on the update and if the code is simple then no it won't add much overhead. It is very common to have trigger functions on table operations.

I would add an before update trigger function and set new.validation_date = old.validation_date. Then in the function code do a check if the user is a validator or not to do that. Do the same for other columns you want to make sure don't change.

You will need to contact support.

Sorry you said blocking production... It is not what I would call common but has seen an uptick here and discord the past couple of weeks from a couple a week. Mainly wanted to make sure you were not using pause/restore instead of restart. I added your ticket to our informal queue an employee monitors when he can. All he can do is move it to infra team queue. You should get a follow up email.

Why was your production plan paused so you had to restore it? You should never Pause a production instance.

It will not resolve on its own typically and needs support.

You will have to wait for support. How long has it been? Free or Pro? We have an INFORMAL escalation path in Discord for projects in such states.

Not really clear what you are referring to or what Google has to do with anything. I assume gmail means your email account is with gmail. It really should not matter who it is thru though for the Supabase dashboad. What sort of issue are you having with your Supabase account?

You will need to generate a support request if you want someone from Supabase to look at your project. What is your full url you are using (masking password and instance (although you already posted that I guess)? Under the Database tab then Settings in the dashboard you can see if there are any bans applied to connections.

What is your login issue? Did you try another browser/device/vpn to rule out a known state issue? You can drop your ticket # here and we have an informal queue in Discord one employee monitors to get project down type issues out of general support queue.

If it is Bolt Cloud then that is managed by Bolt and there is no Supabase direct dashboard for it. You would need to check in their dashboard (if Cloud) or in your Supabase dashboard if not part of their cloud and see if the project status is good or the project is paused.

What does lost access mean? Can't log into dashboard? Blocked for over usage? Project down? Supabase does not monitor here regularly so either post more info to see if a user can offer suggestions or contact support.

Pretty sure that has been supported for quite awhile now.

The team does not normally monitor here. You also posted this on Github and I bumped it to an informal queue we have with 1 of them for project "down" type issues.

I would generate an issue in https://github.com/supabase/realtime/issues . Chances of a dev seeing this here are slim. I've not encountered this before (but I assume the connection will be lost in background and shut it down on invisibility before it errors).

Many users have upgraded to Pro (1 month $25 minimum) and say 7 daily backups are there from while free.

There is a management API issue right now... https://status.supabase.com/incidents/p78yv2qzjm7d

If you can't go back to github then contact support. I don't believe you can switch to email/password if you signed up with Github. support@supabase.com

Please stop posting the same general thing.