Railway Deployment Issue
customtea
HOBBYOP

a year ago

There was an issue with deploying my commits. When I attempted to redeploy the most recent commit (pushed 2 hours ago at the time of writing), the deployment instead reverted to a commit from 1.5 months ago (dated October 16).

I am confident that I selected the most recent commit for redeployment, yet the system deployed the older commit. This has caused significant issues as the outdated code is incompatible with the current database, resulting in disruptions for my users.

I kindly request a thorough investigation into this matter, as it has had a substantial impact on my user base. Thank you.

2 Replies

customtea
HOBBYOP

a year ago

I'd like to provide further information. I redeployed the most recent commit on mobile, specifically on an iPhone. This is the second time it has happened. Thank you!


customtea
HOBBYOP

a year ago

We've did some experiments and found out that if failed deployments are removed from the top of the queue, the system automatically prioritizes other failed deployments further down the queue.

This behavior is problematic, as it results in outdated or unintended code being deployed, causing significant disruptions like what has happened here.


Loading...