Deployments are not detecting new commits
guilherme-am
HOBBYOP

2 months ago

I know this issue has happened before, but I haven't been able to find a solution.

Railway isn't recognizing new commits, so I have to switch to the default branch (develop or main), and then switch back to the target branch to be able to deploy with the latest commit.

Solved

4 Replies

Status changed to Awaiting Railway Response Railway 2 months ago


devrenzz
PRO

2 months ago

Mine is stuck in deploying phase


devrenzz

Mine is stuck in deploying phase

guilherme-am
HOBBYOP

2 months ago

I went to check, and apparently mine is stuck on deployment too. but this is new


guilherme-am

I went to check, and apparently mine is stuck on deployment too. but this is new

devrenzz
PRO

2 months ago

i also experienced the issue you're having right now. i think service is broken as of now but checked https://status.railway.com/ and still there's no update


2 months ago

This is a known issue we're currently tracking. To fix the autodeploy problem, go to GitHub Settings > Applications > Railway App > Configure and verify it has access to the correct repositories, then visit your Railway account settings and unlink and relink the GitHub integration.

Regarding your deployment being stuck, your app appears to have started successfully but the deployment isn't transitioning to an active state. Try redeploying the latest commit via the command palette (Cmd/Ctrl+K > "Redeploy"). If it remains stuck, let us know.

For the other commenter whose deployment is also stuck, please open a new thread so we can investigate your specific deployment.


Status changed to Awaiting User Response Railway 2 months ago


Status changed to Solved guilherme-am 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...