Why did my database stop working?
Last checked 31 Aug 2026
Short answer
A stopped database usually means a broken RLS policy, a failed migration, or (rarely) a paused/disconnected Supabase project — check Logs and ask Lovable to diagnose before changing anything.
Check the obvious first
- Logs: open the database section and look for the failing query and its error message.
- Recent changes: did the last few prompts touch a table, policy, or trigger? Database issues almost always follow a schema or policy edit.
- Connection: if you're using your own Supabase project rather than Lovable Cloud, confirm the project hasn't been paused (free Supabase projects pause after inactivity).
Likely causes
| Symptom | Likely cause |
|---|---|
| Reads return empty/nothing | An RLS policy now blocks the query |
| Writes fail silently | A trigger or constraint rejects the insert/update |
| Everything errors at once | A migration partially applied, leaving tables mismatched |
| Works in Preview, not live | Published version is out of sync with your schema |
Ask for a diagnosis first
The database has stopped returning data for [table/feature]. Check the logs and RLS policies involved and tell me the root cause — don't make changes yet.
Then fix narrowly
Once you know the cause, ask for the smallest fix (one policy, one column default, one trigger) rather than "fix the database", and re-test the affected feature immediately in Preview.
What usually goes wrong
- Broad prompts like "fix my database" invite a large, unpredictable rewrite.
- Role checks stored on a profile column instead of a separate
user_rolestable cause policies to fail unpredictably as data grows — this is a common root cause worth checking explicitly. - If you're on Lovable Cloud you won't have Supabase dashboard access; ask Lovable to run the check for you instead of looking for a dashboard.
- If a migration broke halfway through, use Version history to revert to the last known-good version before retrying.
If the schema has grown complex and repeated fixes aren't sticking, it may be worth having PromptSites.com review the data model properly.
Sources
Was this answer helpful?
Related questions
- AnswerWhy is Lovable chat stuck loading?Chat usually gets stuck loading due to a network blip, a very large/complex request, or a backend timeout. Refresh first, then check the console before resending the same prompt.
- AnswerHow do I fix a Lovable build error?Read the exact error message and file it points to, paste it back to Lovable, and let it fix that specific error rather than describing the symptom vaguely.
- AnswerWhy is my custom domain offline?Custom domains usually go offline because of a missing or changed DNS record, a certificate that hasn't issued yet, or the registrar's records pointing somewhere else — recheck the domain settings and your DNS provider.
- AnswerWhy am I getting "Failed to Fetch"?"Failed to fetch" means the browser couldn't complete a network request at all — usually CORS, a down endpoint, a missing/invalid API key, or no internet connection, rather than a code logic error.
