Your service "App" shows a successful deployment, and there are no error logs present. To ensure commits trigger automatic builds, verify in your service settings that the correct GitHub repo and branch are connected as the trigger branch. If you have "Wait for CI" enabled, a failing or pending GitHub Actions workflow would prevent the deployment from proceeding. You can also manually trigger a deploy via the Command Palette (CMD/Ctrl + K then "Deploy Latest Commit") to confirm the connection is working. More details are in our autodeploys documentation.

[Broadcast] Hey, Angelo here. I'm using a tool to reach out to everyone reporting this issue at once. We've been investigating why auto-deploys and PR environments silently stop triggering, and have traced it to upstream GitHub API requests not being handled gracefully on our end. We've shipped additional monitoring to measure the false positive rate and pinpoint exactly where the issue lies. We'll follow up once we land a core fix. In the meantime, disconnecting and reconnecting your repo at the service level (Settings > Source Repo) is the best workaround. Sorry for the trouble.

Was it solved?

I reconnected the report for the app. It didn't help

Your GitHub integration does not have sufficient repository permissions for us to receive push events. Please go to GitHub Settings > Applications > Railway App > Configure > Repository access, and ensure the relevant repositories are granted access. Then go to your Railway account settings and unlink and relink the GitHub integration.

I did all that and now I have under the repo section

Error

Bad credentials

The "Bad credentials" error means the GitHub token is no longer valid. Please go to your account settings, unlink GitHub, then relink it. Before relinking, confirm the Railway App is still installed at GitHub Settings > Applications > Railway App > Configure. If it's missing, reinstall it and grant access to the relevant repositories, then relink on Railway.