Skip to content
can a recently removed deployment’s ephemeral files be preserved?
legna5003
OP

a month ago

After a deployment at approximately 12:13 UTC on 13 October 2026, our app opened an empty SQLite database. Read-only checks show a volume mounted at /data, but the configured database and upload paths resolved under /app/data. The previous deployment is now marked Removed. The volume contains no database and its uploads directory is empty; no volume backups are listed.

We have made no further deployments, rollbacks, path changes or restore attempts. Could Railway staff urgently advise whether the previous container’s ephemeral filesystem can still be preserved or recovered, particularly /app/data/kmqa.db and uploaded files? We need provider-level recovery guidance, not application debugging.

Please provide a secure channel for additional deployment identifiers and evidence. We will not post customer files or credentials publicly.

Solved

3 Replies

Railway
BOT

a month ago

We don't need any identifiers for this. Your service is linked to your account, and nothing you could send would change the answer.

Files from a removed deployment's container are not something we can preserve, recover or hand back, and we don't restore data lost this way. That includes /app/data/kmqa.db and the uploads.

The volume on the service is mounted at /data. Anything the app writes outside that path does not go to the volume.

To keep data safe from now on, point the database and upload paths at the volume mount. Native volume backups are a Pro feature, so upgrading lets the service restore itself after in-place data loss.


Status changed to Awaiting User Response Railway • about 1 month ago


legna5003
OP

a month ago

Thank you. Please have a Railway staff member confirm whether any provider-level recovery or preservation option exists for the removed deployment. We understand ordinary rollback cannot restore ephemeral storage; please keep this request open pending staff review.


Status changed to Awaiting Railway Response Railway • about 1 month ago


a month ago

There is no provider-level option to preserve or recover files from a removed deployment's container filesystem.


Status changed to Awaiting User Response brody • about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...