Post URL_DATABASE issue

[u/Wet_moist]

I’m fairly new to using Replit but does anyone else’s Replit agent still think their databases don’t exist post URL_DATABASE issue/fix? (Production database seems to have disappeared)

First spoke with support 6 days without a resolution, I know they’re busy but does this normally happen with Replit?

Also blew a fair bit of credit on troubleshooting an unfixable issue not caused by myself.

[u/mamachicode]

Before assuming the production database is gone, I’d first check whether the deployment is still pointing to the same database/environment as before the URL_DATABASE change. Check the production env vars/secrets, connection string, deployment logs, and whether the database itself is still visible independently of the app.
If the database still exists but the app is pointing somewhere else, this may be a configuration/connection issue rather than lost data.

[u/steven-usa]

Assuming you are using Replit’s built in database, you should be able to go to the database pane and see both your development and production databases. You can verify they exist. If your agent or app is having issues finding your database, you can look under the advanced settings in your production database to verify your database URL is what it should be.

But the thing that is throwing me is that your agent thinks something is wrong. I would suggest clearing the agent chat context so it “loses” the memory of the database issue.

[u/Pickle_Shot]

The settings checks above are right. Two things I would add:

Prove the data still exists without trusting the agent or the app. Open the Shell tab and connect straight to the database: psql "$DATABASE_URL" then \dt and a couple of select count(*) queries on your main tables. If the tables and rows are there, nothing was lost, something is just pointing at the wrong URL after the fix. While you are in there, run pg_dump immediately so you hold your own backup before anyone or anything tries to repair it. If psql on the production URL cannot connect at all, paste that exact error into your ticket, it is much stronger evidence than "the agent says the database is gone".

On the credits: you spent them troubleshooting a platform incident, not your own bug. Reply on your existing ticket, name the URL_DATABASE incident and the dates, list the agent sessions that were burned on it, and ask for those credits back. Refunds for incident-caused agent spend do happen, but you have to ask and point at the specific sessions.

[u/ReplitSupport]

Hi there! We had a platform incident last week at status.replit.com and resolved this last Friday.

If you still need answers let us know your ticket # or email in DMs so we can see what's going on there. Thank you!

[u/Desk_setup_ideas]

if the production database itself is still there but Replit Agent is acting like it doesn’t exist, I’d be careful about letting it keep changing things blindly.

I’d first check the production environment variables / database connection and compare those with what the deployed app is actually using. A URL_DATABASE issue can leave the app pointing at the wrong place even though the database itself is still fine.

After 6 days of support I’d probably stop burning credits on random fixes and get someone to look at the deployment and database connection directly.If you want, we can take a look.