We're aware of these transient build queue issues and are actively working on improvements. Please cancel any queued builds and wait a bit before retrying, as additional redeploy attempts can compound the queue.

how much time it will take to resolve this issue ?

We can't provide a specific ETA for these transient issues, but the good news is your recent deployments, including the one you referenced, are now showing as completed. The build queue appears to have cleared. If you hit this again on a future deploy, cancel any queued builds, wait a few minutes, then retry.

will you update me when this done?

Your builds are already completing successfully as noted above, so there is nothing pending to update you on. If the issue recurs on a future deploy, cancel any queued builds, wait a few minutes, and retry.

NO, still I am facing issue not able to deploy

To correct our earlier message, your latest deployment on this service is still showing as failed. Please cancel all queued or failed builds in the service's deployment list, wait 15-20 minutes, then trigger a single fresh deploy. Queuing multiple retries can compound the issue, so a clean slate with one new attempt is the best path forward.

I am not able to understand why this is happening. You are saying everything looks fine but from my end I am not able to deploy a single change. even my backend is also working working fine. will you look into this deeply and resolve my problem.

Your builds are failing at the "Build image" step before your application code runs, so this is not caused by anything in your project. We understand the earlier retry advice has not resolved this over multiple days, and we apologize for the confusion. Please cancel all queued or failed builds and hold off on new deploy attempts for now.

nothing happen you are just wasting my time

We found it. Your new project's grmconnect service has no Root Directory set, so the build looks at the top of your repo, where there's only backend/, frontend/, and config folders, and it can't find an app to build. Your other project works because that service has Root Directory set to backend.

In the failing service, go to Settings, set Root Directory to backend, and redeploy. That should fix it immediately.

Our earlier replies told you this wasn't caused by your project setup. That was wrong, and the first failed builds also showed you no error output, which made this much harder to figure out than it should have been. Sorry for the runaround.

Railway Team