Lovable: Database Load Warnings With One-Click Fixes
LovableLovable now warns when a project's Cloud database is under resource pressure and offers a Resolve button that investigates the cause. Warnings appear in project chat, the Publish dialog, Cloud settings and as a notification to the project owner. Lovable can suggest query or code changes first and offer a resize only when a larger instance is the right fix.
Key Takeaways
- Lovable now flags CPU, memory and disk pressure on Cloud databases using hourly segments over the last 24 hours.
- Warnings surface in chat, the Publish dialog, Cloud settings and an owner notification, and do not block publishing.
- The Resolve button has Lovable find the likely cause and suggest query or code changes.
- The docs advise checking slow queries before paying for a bigger instance.
- When a resize is warranted, Lovable shows the credit impact and asks for approval first.
- Resizing from chat needs Pro or higher, takes a few minutes and briefly restarts the database.
Early warning for an overloaded database
Lovable added high database load warnings for Cloud projects. In More, Cloud, Overview, Advanced settings, the CPU, Memory and Disk cards each show the last 24 hours in hourly segments. A highlighted segment means the resource was near its limit that hour, which Lovable calls "pressure". A single pressured hour may be temporary, so the docs advise checking whether it continues before resizing. The Disk card tracks read and write activity, not how full storage is.
Where warnings appear
If any card shows pressure, Advanced settings displays a "Your database reached a resource threshold" notice with an Ask Lovable button. The Overview shows a "Cloud instance needs attention" notice. Project chat, the Publish dialog and the Cloud Database page show "Your app is under high load" with a Resolve button, and the Publish notice does not block publishing. The project owner also receives a "Database limit reached" notification.
Suggested fixes
Ask Lovable or Resolve makes Lovable check whether pressure continues, find the likely cause and suggest query or code changes that may reduce load, using standard build credits. The docs recommend checking slow queries before upgrading. If a larger instance is the right fix, Lovable shows the credit impact and offers a resize for approval. Resizing from chat requires a Pro plan or higher.
Resizing manually
In Advanced settings, the Database size row has a Manage button. The dialog shows an estimated monthly Cloud cost per size based on the last 30 days of usage. A resize takes a few minutes and briefly restarts the instance, other changes are blocked until it finishes, and the instance can be downsized later. Free plan users must upgrade to move beyond the Tiny size.