We had a deployment pipeline issue earlier today (task queue processing) that was resolved at around 22:40 UTC, and your current deployment was created shortly after at 22:56 UTC. The code snapshot step on that deployment did complete, but the build step has not started yet, likely due to residual delays from the earlier incident. Cancelling this deployment and redeploying should pick up a clean pipeline now that the fix has been in place.

no, just tried and now failing.

running into same issue, cancelled and tried again now its just stuck in queued

Same, just sat at snapshotting code. No progress. Deploy started at this time.

@railway ???

Same issue, still having the snapshotting code problem

Stuck in initializing, @railway

Can you guys try Deploy Latest Commit?

Open the Command Palette (Ctrl-K) > Select Deploy Latest Commit

Builds failing again on Pro and Hobby accounts.

there is no deploy latest commit

Are you using the CLI when deploying?

getting this know instead of the build snapshot , queued due to upstream github issues

This issue is due to issue causing delayed builds - https://status.railway.com/incident/7M7CBL9X

We'll continue to update here. Apologies for inconvenience.

Been very flaky this evening and my builds are stuck too

Hi. I've got the same problems. Tried both with cli and github push but everything is stuck at initializing/queued

Same issue on US-East, build approaching 30 minutes, usually takes a couple of minutes.

I deploy with a github actions pipeline because Railway wont let me add github repos from another github account

stuck on queued status

any updates?

wtf are we paying for again?

Unfortunately, incidents can occur, guys. Let’s hope for a fast resolution.

What's going on?

I've been waiting for deployment for an hour and a half already! This is insane, is there an ETA?

Is this issue resolved ? I am stuck with the same issue

Can you give more context and logs? Perhaps open a new thread, this was resolved last night but we are monitoring for recurrence.

created a new thread

Closing the loop here. The pipeline issue was resolved at 02:17 UTC and deploys have been stable since. I checked your service directly, your latest deploy this afternoon went through fine. Sorry about the rough evening. If anything gets stuck again, open a fresh thread and we'll jump on it.