a month ago
Hello Railway Support,
I urgently need help recovering a SQLite database from a removed Flowise deployment.
Project ID:
96398c48-984e-4a6b-a8a6-34b1019e550e
Service ID:
2954766d-b923-4940-ada2-d155c341f608
Environment ID:
98ed8e90-9dd9-424a-8ac9-6858b8090d7d
File that needs to be recovered:
/home/node/.flowise/database.sqlite
The working deployment was replaced on September 8, 2026, approximately between 07:00 and 08:00 UTC. It contained my latest Flowise chatflows, credentials, and configuration.
A Railway volume existed, but it was incorrectly mounted at:
/root/.flowise
Flowise was actually storing its database at:
/home/node/.flowise/database.sqlite
Therefore, the database was stored in the previous deployment’s ephemeral filesystem instead of the persistent volume. The deployment has now been removed, and the new deployment started with an empty database.
Could you please check whether the filesystem, container snapshot, or database.sqlite file from the immediately preceding removed deployment can be recovered? Even a downloadable copy of the file would be enough.
This data is important and the removal happened only recently. Please avoid restoring over the current service; I would prefer receiving the recovered database as a downloadable file or in a separate volume/location.
Thank you.
Attachments
3 Replies
a month ago
The Flowise AI service does have a volume, but it is mounted at /root/.flowise, while Flowise writes its database to /home/node/.flowise/database.sqlite. Because that path falls outside the volume mount, the SQLite file was stored on the container's ephemeral filesystem, which is discarded when a deployment is replaced. We are not able to recover data that was only in ephemeral storage. Your volume at /root/.flowise is intact with its contents (about 49 MB), so to prevent this going forward, update the volume mount path to /home/node/.flowise so Flowise's data lands on persistent storage.
Status changed to Awaiting User Response Railway • 27 days ago
Railway
The Flowise AI service does have a volume, but it is mounted at `/root/.flowise`, while Flowise writes its database to `/home/node/.flowise/database.sqlite`. Because that path falls outside the volume mount, the SQLite file was stored on the container's ephemeral filesystem, which is discarded when a deployment is replaced. We are not able to recover data that was only in ephemeral storage. Your volume at `/root/.flowise` is intact with its contents (about 49 MB), so to prevent this going forward, update the volume mount path to `/home/node/.flowise` so Flowise's data lands on persistent storage.
a month ago
osea digame ya se borro mis chatflow? no hay manera de recuperarlo?
Status changed to Awaiting Railway Response Railway • 27 days ago
a month ago
Apologies, we only correspond in English. Please open a new thread in English.
Status changed to Closed Railway • 27 days ago