deployment FAILS BACK AGAIN IN 5 MUNITES AFTER DEPLOYMENT SUCCESSFULLY
nitinpde
HOBBYOP

a year ago

my railway failed due to transaction problems in payment once . by resolving that we no noticed we lost all our data & we were unable to restore here are some pics , sometime the deployment restores & fails back again.. i think hostinger or other platforms are easier and support friendly we are unable to recover over n8n deployments & lost other details i think the lack of support for non technical users is worst thing in railway

$10 Bounty

4 Replies

Railway
BOT

a year ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


clashing
HOBBY

a year ago

Hi buddy, there are no attached pics with your query (please copy and paste the concerned images). If you do not have volumes attached to your services, then there would be no data-retention. https://docs.railway.com/guides/volumes

When you attach a volume to your Railway service, the data stored on that volume is persisted independently of the lifecycle of your service instance (survives crashes and redeployments of your service). Backups for the volumes are also there, thus covering any edge case in helping you to not lose data access


clashing
HOBBY

a year ago

Did this helped, nitinpde


clashing

Hi buddy, there are no attached pics with your query (please copy and paste the concerned images). If you do not have volumes attached to your services, then there would be no data-retention. <https://docs.railway.com/guides/volumes> When you attach a **volume** to your Railway service, the data stored on that volume is **persisted independently** of the lifecycle of your service instance (**survives crashes and redeployments of your service**). Backups for the volumes are also there, thus covering any edge case in helping you to not lose data access

clashing
HOBBY

a year ago

nitinpde, any progress!


Welcome!

Sign in to your Railway account to join the conversation.

Loading...