2 months ago
Project: dealercrm-backend
Environment: production
Service: dealercrm-backend (dealercrm-backend-production.up.railway.app)
Repo: RealDealerAI/dealercrm-backend, branch: main
Issue:
Deployments triggered by GitHub pushes are stuck in QUEUED, showing "Deployment queued due to upstream GitHub issues." They never progress to build. Same symptom as a thread from ~8 hours ago marked Solved — but still occurring for me now.
Timeline:
- Stuck 30+ minutes across multiple pushes
- Affected commits: 00772db, and two later empty commits (abd0b55, b4191fe) pushed specifically to retrigger — all stuck
- An earlier deployment completed fine before this started
Already checked:
- githubstatus.com shows no outage (all green)
- status.railway.com shows fully operational
- Billing fine, usage under $1, credit remaining
- Pushed fresh empty commits to force redeploy — same result
- No changes to GitHub App install or repo permissions on my end
Ask:
Please check whether Railway's GitHub App connection/webhook for this repo lost access or hit a rate limit, and restore normal auto-deploy. Happy to provide deployment IDs or logs.
1 Replies
2 months ago
Your most recent deployments on this service show as completed, so the queued state appears to have cleared. For future occurrences, you can bypass GitHub-triggered deploys by opening the Command Palette (CMD/Ctrl + K) and selecting "Deploy Latest Commit" to trigger a build directly. Also note that your service uses a root directory (dealercrm-backend-v2/dealercrm/backend), and empty commits do not change any files in that path, so they would not trigger a new deployment even under normal conditions.
Status changed to Awaiting User Response Railway • 2 months ago
Status changed to Solved rdai-admin • 2 months ago