a month ago
Project ID: 30b369be-3f4a-4d0f-a4d7-2efafc486f26
I'm unable to deploy a new commit to my project on Railway. After pushing an update to my connected GitHub repository, the deployment is stuck in Queued status with the message:
"deployment queued due to upstream Github issues"
This has been stuck since 08:10 UTC. I'm currently using the trial version and I still have 16 days or usage credits left.
I tried the following steps:
- Disconnected and reconnected the repository from the service settings
- Fully disconnected my GitHub account from Railway
- Uninstalled the Railway GitHub App from my GitHub organization
- Reinstalled the Railway GitHub App on the organization and re-authorized repository access.
- Reconnected the repository to the service in Railway.
5 Replies
a month ago
The "deployment queued due to upstream Github issues" message indicates a transient condition that resolves on its own. Cancel any queued deployments and wait before redeploying, since additional deploys can compound the queue.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
As instructed, I canceled the pending operation. I waited a while and submitted the commit again. However, it still remained as "QUEUED".
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your workspace is currently in an INACTIVE state, which is likely why deployments are queuing rather than this being a GitHub-related issue. You can check and resolve your subscription status at your workspace billing page.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
No, my workspace is active. On the billing page, my account shows as trial active, and I currently have a 16-day trial period and a balance of $3.75. The system, which was working fine until an hour ago, suddenly stopped deploying. I don't think this is related to my account's subscription status.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This was on our side, sorry for the runaround. A backlog in our deployment queue this morning held trial deploys in QUEUED, and the GitHub error message was misleading. Nothing you did with the repo or GitHub app caused it. The backlog cleared and your service deployed successfully this afternoon. If anything gets stuck again, let us know.
Railway Team
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved sam-a • about 1 month ago