Carol Monroe
← Field Notes

Lovable Cloud Database Stuck? Here's How to Fix It

Mar 26, 2026 · 4 min · Workaround 324 views

The problem

You open your Lovable Cloud panel and something's wrong. Your database isn't responding, queries are timing out, or you see the dreaded "Error loading backups" message.

Error loading backups

This happens more often than you'd think. Instance resizes get stuck, connection pools exhaust, or the database just stops responding. And since you don't have direct dashboard access on Cloud, your options feel limited.

But there's a workaround that works.

The fix: Instance refresh

This was discovered by the community and it's saved a lot of people. The idea is simple - you trigger a resize by changing your instance tier, which forces a full platform refresh.

Step 1: Go to Advanced Settings

From your Cloud panel Overview, scroll down and click Advanced Settings.

Overview - click Advanced Settings

Step 2: Open the instance dropdown

You'll see your current instance size. Click the "Select an instance size" dropdown on the right.

Advanced Settings - click the dropdown

Step 3: Select a different tier

Pick the next tier up from your current one. If you're on Tiny, select Mini.

Select Mini from the dropdown

Available tiers: Tiny (trying things out), Mini (early projects), Small (room to grow), Medium (regular use), Large (higher demand). See the Lovable Cloud docs for details on scaling.

Step 4: Confirm the resize

Click Upgrade Instance. You'll see a confirmation dialog showing what to expect.

Confirm instance resize

Step 5: Wait for the resize

You'll see "Instance is being resized. This typically takes less than 2 minutes."

Instance being resized

Step 6: Downgrade back (but not too fast)

Once the resize completes and your database is working again, you can downgrade back to your original tier so you don't stay on a more expensive plan. You'll see the "Downgrade instance" option now available.

Instance resized successfully - now downgrade back

Important: Don't rush the downgrade. Give it some time before switching back. If the same error comes back after downgrading, stay on the larger tier - your app might actually need the extra resources. Resizing too quickly back and forth can cause issues.

About costs

Upgrading your instance temporarily will use some of your Cloud balance ($25/month included on paid plans). Lovable doesn't publish exact prices per tier, but a quick upgrade and downgrade shouldn't have a big impact. Check your Cloud & AI balance after to see the cost. Your Cloud costs are broken down by category (database server, storage, compute, etc.) so you can see exactly what's using your budget.

When this works

  • Database not responding or timing out
  • "Error loading backups" in Advanced Settings
  • Instance resize stuck for hours
  • Connection pool exhausted
  • Queries returning nothing after a deploy

When this doesn't work

If the instance refresh doesn't fix it, you're looking at an infrastructure issue that needs the Lovable team. Email support@lovable.dev with:

  • Your project ID
  • Screenshot of the error
  • How long it's been down

How to prevent it

  • Don't open database connections before filtering in webhooks or edge functions - filter first, then query
  • If your app is growing, consider upgrading your instance tier permanently instead of staying on Tiny
  • For production apps, Tiny is great for development but production traffic needs room to breathe

Useful links

lovable · lovable-cloud · workaround

XLinkedIn

Reader margin

What stayed with you?

0 notes

Leave one small mark in the margin.

Notes from readers

The margin is open. You can leave the first note.

Stuck with something like this? I fix it daily → Services

© 2026 Carol Monroe · Services delivered through Moonshot Labs LLCPrivacy · Terms · RSS · X · LinkedIn ·
Carol Monroe · visitor ledgerThe logbook

Leave a little note before you go.

Notes left hereopen since 2026

The page is ready for its first note.

Your page280 characters

Glad you found your way here.

Tell me what brought you in, what stayed with you, or simply say hello.

0/280 · your note will be public