Hello,

Your database does not have a volume, you deleted it 7 weeks ago -

Without a volume data cannot persist.

Since this was an action you initiated, we cannot help with any data recovery.

So that this doesn't happen again in the future, I have staged a change to add a volume back to your database.

Please feel free to click the Deploy button so that you don't lose data in the future.

Note that deploying the staged change will clear the data that's currently in the database, but after that, data will be safe.

Best,
Brody

I understand what happened now. Every time I deployed, the volume was detached—I first noticed this with my n8n container. Later I switched to your managed PostgreSQL, but I didn’t see that the volume still wasn’t attaching, so the same problem occurred.

I think this was an issue when deploying containers with volumes to metal regions. Because my account’s default region was set to a metal region, it seems that—even though I explicitly picked a legacy region—the service was deployed behind the scenes to metal and hit the same volume-attachment problem.

You can see the failed attachment attempts in the project logs.

Thanks for looking into this!

I just checked and it looks like you've now correctly attached your volume -- did you need additional help here?

Hello,

I just want to clarify that there are no volume attachment problems, you simply deleted the volume 7 weeks ago.

Best,

Brody

All good!

Bad customer support. Bad comment, and bad deployment at the time (stuff happens sometimes and it is what it is). Makes no sense to continue the discussion but you have no idea what happened. Maybe you’re not the right person to say that

Brody, this happened seven weeks ago. I tried to deploy a single n8n instance with a volume, but I couldn’t get it to work.

1. I selected a legacy region and clicked Deploy.

2. The deployment failed.

3. When I reviewed the settings, the region had somehow switched to a metal region.

4. It turned out the deployment was using the global default region in my account, and there was no way to change it back to a legacy region.

5. I retried several times—same result.

Eventually I gave up and used your Postgres template instead; that deployed without errors. I assumed everything was fine, but there were no volume-related warnings, so I lost all the project data.

The points above are real. Please check your systems—this looks like a bug in user feedback and migration (from seven weeks ago). For the record, I didn’t delete the volume back then, so that’s not the cause.

Hear you here vic, and understand your frustration that the defaults from the templates didn't set you up for success.

First I want to make sure that right now you're current state is good, then we can move into feedback and improving the product.

Hi echohack,

The root cause was a bug that happened seven weeks ago. If you check the logs, you’ll see the volume was deleted immediately—one of your background processes removed it automatically.

I’m fine for now, and I appreciate your reply (unlike the other person’s). Please coach your team to remember that no system is perfect, and they shouldn’t make assumptions without more information.