Hi, I’m trying to recover data from a Railway persistent volume after my trial/billing period ended.

I had a small Flask + SQLite app running successfully on Railway. The SQLite database was stored on a persistent volume mounted at /data.

Before the service went offline, users had already populated the database. After I reinstated billing and redeployed the service, the app came back online but the database appeared reset.

Current setup:

Environment: production

Service has a persistent volume attached

Mount path: /data

Current volume contains:

.flask_secret

lost+found/

secret_santa.db

I downloaded the current secret_santa.db and inspected it locally. The database is valid, but the participants table is empty and the app state is reset, so this appears to be a newly initialized database rather than the one used before the billing interruption.

I have also checked:

Backups: none available

railway status: no detached volumes shown

railway environment list: only production

/data/lost+found: empty

no older local SQLite copy found

There are older deployments from before the interruption, but I understand redeploy/rollback would restore code/config, not historical volume contents.

Is there any way Railway can confirm whether the original persistent volume or an older retained copy of its data still exists server-side from before the billing/trial interruption?

I have not intentionally deleted the volume or database.

I can provide Project ID / Service ID / Volume ID privately if a Railway staff member needs them.