Yes, ephemeral storage is lost at redeploy. To persist data between deployments, you'll need to use Volumes. Please take a look at the Flowise-Railway-Volumetemplate, which includes a Flowise service configured with a Volume .

I am NOT using ephemeral storage; I have been using the template with a volume; I lose ALL settings when upgrading. I am sorry if I did not explain it correcty, but you have the screenshot. I need to upgrade version and I cannot

here's another screenshot that complements the previous one

Hello,

You have the wrong mount path for your volume, which would cause Flowise to write data to ephemeral storage instead of the volume.

Best,
Brody

I have updated the path to /opt/railway/.flowise and upgraded the Flowise version. Now, I trust that my settings will remain intact. Is that accurate? Additionally, when I click on "FlowiseAI-Railway" what exactly am I backing up?

5 days to respond?

I HAVE BEEN WITHOUT SERVICE FOR TWO WEEKS WITHOUT A SOLUTION FROM YOU - SEE SCREENSHOTS. YOU FAILED TO DO A MIGRATION. OUR COMPANY IS INCURRING COSTS BECAUSE OF THE LACK OF SUPPORT. PLEASE LOOK AT THE SCREENSHOT AND SEND YOUR LEGAL ADDRESS

Hello,

The original issue was related to application configuration rather than a platform or product issue, so it falls under community support without a guaranteed response time.

Regarding the failed migration - that's a separate issue and should have been posted as a new thread, as this thread is designated for community support only.

However, I've gone ahead and completed the migration for you.

Best regards,

Brody

I downgraded my account account after losing a substantial amount of time and data trying to solve this. I was forced to delete most services. I was happy and I became very frustated trired of wasting my time and money