An unknown error occurred
patstlouis
PROOP

2 months ago

Hello, I have deployed a new environment for one of my projects. It's the second time it gives me this error. Everything gets deployed fine, I can browse my app, services are healthy, then when I come back alter I have this notification and everything is set as "new"

image.png

Attachments

14 Replies

patstlouis
PROOP

2 months ago

its all the services in the environment, other environments are fine, this one everything gets "reset" periodically it seems. Database gets wiped, everything becomes new again after it was deployed succesfully


2 months ago

It looks like some of the branches you are trying to deploy don't exist.


patstlouis
PROOP

2 months ago

I "duplicated" the environment from my development, and I change all branch in this new environment to deploy. It deploys fine, then some time later, reverts to this "new" state and reverts all branches to their original development / feature branches which in fact don't exist anymore. It did it again this morning. I might just create a whole new environment and avoid the "duplicate" feature, which I think might be causing the issue.


patstlouis
PROOP

2 months ago

so here it is deployed

image.png

Attachments


patstlouis
PROOP

2 months ago

I can access all services


patstlouis
PROOP

2 months ago

then 30 seconds later

image.png

Attachments


patstlouis
PROOP

2 months ago

hmmmm.... ok so I did "discard all changes", and now everything is back to being fine. There's definitly something odd with the duplicate feature I think


patstlouis
PROOP

2 months ago

its like trying to push globacl changes


patstlouis
PROOP

2 months ago

in the environment


2 months ago

I remember getting that issue on some PR environments, let me see if I have one up still


2 months ago

I have one but it's different, though I vividly remember experiencing the same issue as you. I will keep monitoring.

image.png

Attachments


patstlouis
PROOP

2 months ago

interesting


patstlouis
PROOP

2 months ago

after discarding the changes, it seems stable now


2 months ago

This specific error has since been fixed, at least according to the monitoring we had for it.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...