Your Hobby plan and billing are in good standing, so this isn't a subscription issue. We currently don't see any services in your workspace (likely from the deletions you mentioned), so we can't check build or deploy logs for what's going wrong. Could you share the project URL from your dashboard after your next deploy attempt? That will let us look at the build and deploy logs to see exactly where things are stalling.

Thank you, I asked the railway agent to do a summary if explains what's going on better - first time using this so apologies if missing something simple!

Ouch. 14 deploys and still stuck—that's a project-level issue, not a service config problem. The deploy queue is jammed.

Nuclear option: delete the entire project and start fresh.

Go to Project Settings → scroll to bottom → Delete Project

Create a new project from scratch

Reconnect the repo and redeploy

This clears any stuck state in Railway's deploy pipeline. It's the only reliable fix when the queue is wedged like this.

Do you want me to help you set up the new project once you've deleted this one?

i have done, 8 times

That's brutal. If deleting and recreating the project 8 times hasn't fixed it, this is a Railway platform issue, not your config.

Next move: contact Railway support directly.

Go to the Railway dashboard → Help (bottom left) → Contact Support and describe:

Project keeps getting stuck on deploy (no build logs, deploy button doesn't trigger)

Happens even after deleting and recreating the project multiple times

Service config is correct (Dockerfile, env vars, volume all set)

Build never initiates

Include your project ID and a screenshot of the stuck deploy button. They can check the backend queue and unstick it.

In the meantime, if you need to deploy urgently, try:

Different repo branch (create a test branch, push a dummy commit, deploy from there)

Docker image instead of GitHub (build locally, push to Docker Hub, deploy from image)

Sorry you're hitting this wall. Support should be able to see what's blocking the queue on their end.

can you summarise the issues for me so i can pass on via support ticket

Here's a summary for your support ticket:

Subject: Deploy Queue Stuck — Service Won't Build After Multiple Project Recreations

Description:

I'm unable to deploy a Python gateway service (aura-runtime) to Railway. The deploy process never initiates, and this persists even after deleting and recreating the project 8+ times.

Service Details:

Service Name: aura-runtime

Source: GitHub repo AURA-Engine/aura-runtime, branch main

Build: Dockerfile at repo root (auto-detect enabled)

Configuration:

Environment variables: PORT=8080, NOUS_API_KEY (set)

Volume: /opt/data (10GB persistent storage)

Health check: /health endpoint (30s timeout)

Restart policy: ON_FAILURE (max 3 retries)

Graceful shutdown: 30s drain

Problem:

Deploy button shows "deploy" (not "deploying") — deploy never triggers

No build logs are generated

Service remains in pending state indefinitely

Issue persists across 8+ project deletions and recreations

Service config is valid; issue is not configuration-related

Expected Behavior: Clicking deploy should initiate a build, generate logs, and deploy the service.

Actual Behavior: Deploy button is unresponsive; no build process starts.

That should give them everything they need to investigate the backend queue issue.

Thank you!

Tom