38 minutes ago
Hi Railway Support,
I'm experiencing an issue with my TRAC51 Conference Companion deployment.
My latest deployment has remained in QUEUED status and never progresses to Initializing or Building. No build logs are generated.
Details:
- Platform: Railway
- Account: Trial plan
- Trial balance: Credits remaining, approximately 4 days until trial expiry
- Service: TRAC51-Conference-Companion
- Source: Connected private GitHub repository
- Branch: main
What I've verified:
- GitHub is successfully connected to Railway.
- Updated files and commits are visible in Railway.
- GitHub application permissions are correct.
- I've manually triggered Deploy Latest Commit.
- There is no Limited Access indicator.
- The existing v2.3 deployment remains active and operational.
- New deployments remain queued without generating build logs.
Could you please investigate whether my workspace or service is stuck in the deployment queue, and help unblock or reprocess the deployment?
I can provide the project ID, service ID, deployment ID and commit SHA if required.
Thank you.
1 Replies
36 minutes ago
Your newest TRAC51-Conference-Companion deployment, created at 08:12 UTC today, is still queued, but none of your workspace's 3 build/deploy slots are in use. That means it is not waiting behind your other deployments, and your trial's concurrency limit is not what is holding it.
Separately, GitHub connections were revoked during the October 21 incident, and the documented recovery for deploys from a connected repository is to reconnect GitHub in Account Settings, confirm the Railway GitHub App still has access to the repository, disconnect and reconnect the repository in the service's Settings, and then run Deploy Latest Commit.
Your v2.3 deployment keeps running in the meantime.
Status changed to Awaiting User Response Railway • 36 minutes ago