working environment duplicates to failed deployment
sinscrit
PROOP

10 months ago

hi, I duplicated my production environment but it fails to deploy.
I do get some errors but I they are not pertinent to the currently deployment.

What I am guessing is the process did not duplicate my current production deployment but some other previously failed deployment.

As back story my previous updates to the prodcution failed so I had to perform a rollback. The rollback is what is currently deployed. However I am guessing that the duplication ignores the rolled back deployment and duplicated the previously failed deployment.

Solved

3 Replies

echohack
EMPLOYEE

10 months ago

Ah, are you using the Sync Environments feature? That should fix this issue for you: https://docs.railway.com/guides/environments#sync-environments


Status changed to Awaiting User Response Railway 10 months ago


Status changed to Solved echohack 10 months ago


sinscrit
PROOP

10 months ago

Unfortunately, that does not help. The production environment I want to sync with is disabled in that screen.
THat is the production environment that I duplicated in the first place.

Attachments


Status changed to Awaiting Railway Response Railway 10 months ago


echohack
EMPLOYEE

10 months ago

Oh I see now, it is synced but tried to redeploy your services instead of mirroring your production environment. Since you rolled-back production by hand, you'd also need to rollback your staging environment to mirror production in the same manner.

Typically folks will tie their environments to a github branch (For example, for your staging environment, tying it to a staging branch). Currently you're tied to main so it will automatically deploy whatever the latest version of your main branch is just like production will.


Status changed to Awaiting User Response Railway 10 months ago


Railway
BOT

7 months 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 7 months ago


Loading...