Hi everyone,

I'm hoping someone from Railway can help determine whether this is a platform issue or something specific to my workspace.

Project details

Plan: Hobby

Region: US West

Single service project (only one service in the project)

Problem

A deployment has remained in the queue for over 30 minutes without ever starting.

The deployment never reaches:

Initialization

Build

Deploy

Post-deploy

It simply stays in Queued / Processing deployment...

There are no build logs at all, which suggests the deployment has never been assigned to a build worker.

Things I've already verified

Only one service exists in the project.

Only one deployment is currently queued.

No other deployments are running.

I'm well within my Hobby plan usage/credit limits.

Build concurrency shouldn't be a factor because nothing else is building.

I removed the original queued deployment and pushed a new commit. The new deployment behaves exactly the same.

Railway's AI assistant also confirmed there are no build logs and that the deployment has not started.

From my perspective, the deployment never reaches the point where Railway even begins downloading or building the application.

Has anyone experienced this before, or is someone from Railway able to check whether my workspace or deployment is stuck in the scheduler?

I'd be happy to provide the deployment ID privately if needed.

Thanks!