2 months ago
Hello Railway Support,
Our production service remains online, but every new deployment is blocked.
Project: terrific-transformationEnvironment: productionService: sem-clt-turbo-backendRepository: phbarboza/sem-clt-turbo-backendBranch: mainRegion: US WestProduction domain: app.vidasemclt.com
Symptoms:
GitHub deployments remain indefinitely in QUEUED.
Railway displays: Deployment queued due to upstream GitHub issues.
A deployment made through Railway CLI also remained indefinitely in INITIALIZING, at Taking a snapshot of the code.
The CLI deployment was removed after approximately 25 minutes.
Disconnecting and reconnecting the GitHub repository did not resolve the issue.
GitHub authorization and automatic deployments are enabled.
The current production deployment remains healthy and ACTIVE.
Affected GitHub deployments:
chore(deploy): trigger Railway after source reconnect
fix(meta): preserve ad account selector after OAuth
Removed you please inspect and clear the deployment queue/snapshot state for this service and verify the GitHub integration on Railway’s side?
Please do not remove or restart the currently ACTIVE production deployment.
Thank you.
1 Replies
2 months ago
We're sorry for the trouble. There is currently an active incident, "Deployments are slow to progress," affecting deployments across all regions including US West. This is causing deployments to remain in a queued or initializing state longer than expected, which matches what you're seeing. Your active production deployment will not be affected. You can follow updates here: Deployments are slow to progress
Status changed to Awaiting User Response Railway • about 2 months ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago