Did you try redeploying it?

Yes i am clicking on redeploy already

Click that purple button on the side of the screen and type "Redeploy"
If it's a Docker image it will show "Redeploy source image" click it

Otherwise if it's a repo it will show "Redeploy latest commit"

I clicked on redeploy latest commit

Can you check the logs and paste it herE?

[Region: us-west1]

╭─────────────────╮
│ Railpack 0.17.1 │
╰─────────────────╯

⚠ Script start.sh not found
✖ Railpack could not determine how to build the app.

The following languages are supported:
Php
Golang
Java
Rust
Ruby
Elixir
Python
Deno
Dotnet
Node
Gleam
Cpp
Staticfile
Shell

The app contents that Railpack analyzed contains:

./
├── forgotPassword.js
├── login.js
├── otp.js
└── register.js

Check out the docs for more information: https://railpack.com

Is the repo public? What language is it?

its private / node js

Is it pointed to the root path at the service settings? Railpack is unable to identify the language thus resulting in a failed build.

It needs to detect the package.json at the root directory

I haven’t made any changes to the project structure, repository, branch, or Railway settings for a long time. The service was building and deploying successfully earlier (around 5 PM), and then suddenly started failing with this Railpack error.

The package.json is still in the same location as before, and nothing was moved or renamed.

Could you please check if there was any recent change or issue on Railpack’s detection side? It seems Railpack is no longer detecting the project correctly even though the structure has not changed.

It does have a package.json at root, but I wonder if the builder is set to point at that because it logs these files:

./
├── forgotPassword.js
├── login.js
├── otp.js
└── register.js

I am sure this is not a Railpack issue

Hello,

We had an incident earlier that caused some running workloads to be unexpectedly terminated while the status in the UI didn't properly update. This has since been resolved, but in some cases, you may need to redeploy your services.

You can find the post-mortem for the incident here: https://blog.railway.com/p/incident-report-february-11-2026

Our deepest apologies for the inconvenience this has caused.