Your services are currently in the "Initializing" state, which means they are queued for building. During periods of high traffic, deployments for Hobby plan users may be temporarily queued while Pro/Enterprise users are prioritized. Once capacity frees up, your queued deployments will automatically process in order without any action needed on your part. You can read more about this in our deployment docs.

Same for me, diagnostic :

Retrigger the deployment to resolve this. The build was scheduled on a Metal builder but never executed, producing only a single scheduling log line with no actual build output. The code changes in this commit are valid TypeScript additions and are not the cause of the failure.

My deployments have been queued for more than 48 hours and does that mean we can't use railway again as hobby users, if you can't offer service to hobby users why still keep it as a plan, ive used railway for sometime and I'll be hurt to change to another platform that will respect its customers a little bit and there's more than enough available

Thank you

Yep, this was a bug that has since been resolved. Sorry about that.

But deployments are still queuing, do I have to kill all of them and make a new deployment?

We're aware of these transient build queue issues and are actively working on improvements.