Deployment issue: **Problem:** * Latest commit: 1ee675e * Backend deploying: 9f2278f (old code) * Frontend deploying: d006908 (old code) **What I've tried:** * Multiple GitHub redeploys (still gets old commits) * CLI deployments with npx railway up (still gets old commits) * Fixed railway.toml config files * GitHub disconnect/reconnect **Result:** Railway consistently ignores my latest code, causing 404 errors and broken functionality. Both services are stuck deploying old commits even with CLI deployments. It took me dozens of pushes to realize what was happening here. I am on the Hobby plan, but I have used less than $1 at this point so I should still have room, I think?

Ignoring latest commit - Railway Central Station

Ignoring latest commit

the-cultured-swine

HOBBYOP

10 months ago

Deployment issue:

Problem:

What I've tried:

Result: Railway consistently ignores my latest code, causing 404 errors and broken functionality.

Both services are stuck deploying old commits even with CLI deployments. It took me dozens of pushes to realize what was happening here.

I am on the Hobby plan, but I have used less than $1 at this point so I should still have room, I think?

Solved

2 Replies

Railway

BOT

10 months 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!

the-cultured-swine

HOBBYOP

10 months ago

Turns out, there was a very small typo in the yaml file causing the issue. All sorted out

Status changed to Solved the-cultured-swine • 10 months ago

Welcome!

Sign in to your Railway account to join the conversation.