Please take a look please! Environments are not consistently tracking deploys to branches right now. I just setup a new environment in my production environment and I have to manually deploy it everytime now

Hi, we're tracking this. It's a known issue where subsequent pushes to PR branches aren't triggering redeploys. Our engineering team has identified the root cause and is working on a fix. For now, could you please try disconnecting and reconnecting the repo to trigger a deploy.

We found and fixed a bug that broke GitHub connections for some services when forking environments or creating PR environments. We've restored connections across all your project's environments (31 total). A recent push to main has already deployed successfully across your services. New PR environments going forward will also correctly set up their connections. Sorry for the inconvenience.

thank you! please please acknowledge this in your status tracker in the future --- this is a pretty critical function. we've been moving a lot slower this week as a result

Totally understand the frustration from your side this must've felt like an outage since it was hitting your workspace consistently, which was really unlucky

This was a narrow bug that unfortunately affected a very small subset of PR environments, so it didn't meet the bar for the global status page (which we reserve for platform-wide incidents).

That said, your feedback on how we communicate issues that impact a smaller set of users is heard.

Sorry again for the slowdown this week, and appreciate your patience while we tracked it down!

Circling back here --- it recovered a bit Sunday/Monday but most of my PR environments are behaving the same again (not re-deploying when changes are deployed)

Sorry to hear it's regressed. Teams been a bit busy elsewhere.

I just ran an investigation on the issue and traced the code paths, it looks like an issue with how we handle transient GitHub API failures. I have a concept PR with a fix and going to get this discussed with the team.

Hi, I've noticed that the Railway GitHub App Installation for your organization is missing updated permissions. We updated the app permissions a while ago, but they need your approval.

Could you please do the following:

1. Go to your GitHub Organization Settings
2. In the sidebar, find Third-Party Access -> GitHub Apps
3. In the list of installed GitHub Apps, find "Railway App". You should see it saying "Permission updates requested"
4. Click on "Review request" and accept the new permissions
5. Then reconnect the services

We require these permissions to continuously check that your workspace has access to the repo. Without these permissions, our system can't verify access, and will not auto-deploy. This is a safety measure to prevent that someone who used to have access to the repo, but has no access anymore, could still deploy your repo, and thus would still have access to your code.

You should've gotten an email from GitHub a while ago, prompting you to accept the new permissions. We will work on showing this notification in our Dashboard as well.