Project Stuck in “Pausing” State for hours
Hey, has anyone experienced a project being stuck on “Pausing…” for hours? I tried to pause it after dealing with repeated 500 errors and recovery mode logs. Is this normal, or should I take any action?
4 Replies
Pausing a flakey project is a bad idea versus just restarting it.
Small projects should pause in a few minutes.
Try a different browser to make sure not just a browser state thing.
Support will be only option if stuck.
Support will be only option if stuck.
Thanks for the reply! I actually already tried restarting the server a few times before deciding to pause it — I kept getting 500 errors, and the logs were repeatedly showing "the database system is in recovery mode" messages.
The project isn’t live yet, it’s still in development — just the schema is set up, no real data yet. I figured pausing and restoring from a backup might help, but it’s now been stuck on “Pausing…” for several hours, even after trying a different browser.
I realize pausing may not have been the best move, but I was running out of options.
Any ideas on what might have caused the 500 errors and the recovery mode state in the first place? Would love any suggestions or things I can look into.
I don’t. Read only mode would be if you exceed DB size.
That seems like Postgres itself crashed. There might have been info in the Postgres logs.
That seems like Postgres itself crashed. There might have been info in the Postgres logs.
thank's a lot
My issue was resolved by Supabase support.
They said the problem was caused by a crash-loop during access to a replication slot. They fixed it temporarily by dropping the faulty slot.
A new version of OrioleDB (17.5.1.001-orioledb) will be released next week, and they recommend upgrading by pausing/restoring or using the upgrade option in the dashboard once it’s available, for a permanent fix.