New deployments triggered on the website seem to ignore the deployment settings
Our instances are on US-1 and we have Dockerfile set for several projects. When clicking "redeploy" on the most recent successful deployment, the nixpacks build gets triggered. This seems to be related to the outage
9 Replies
Project ID:
120b5ec5-59d8-4087-84ae-4e0b3d934aa7120b5ec5-59d8-4087-84ae-4e0b3d934aa7
while I can't rule out this being related to the ongoing incident, this sounds more like what another user reported a few days ago where they used the redoploy button in the 3 dot menu of the most recent deployment and it went and deployed some really old deployment
this issue can be prevented by using this https://bookmarklets.up.railway.app/service-redeploy/
it will cause railway to redeploy from the linked repo and branch instead of redeploying whatever old deployment
@matt - another case of the 3 dot menu redeploy button deploying an old deployment
I see
@theodor
fyi
@Brody Redis connection seems to be completely down
Is this also part of the incident
yeah thats for sure due to the ongoing incident
railway is heads down getting deployments restored
If we swap out the Reids instance to a new one, would it be fixed
no guarantee, a new redis might fail to deploy all together
added this bug to product's traqige board
Hey @unstoppablerizz
Our incident is resolved and your services should be back up again.