24 days ago
After revoking and re-authorizing the Railway GitHub App, automatic deploys triggered by pushing to a branch get stuck at "taking a snapshot of the code" indefinitely and never progress to the build step.
Key observations:
- Manual redeployment from the Railway UI works correctly every time
- The issue affects all branches connected to the service (both main and int)
- The problem started immediately after I had to revoke and re-authorize the GitHub App due to "Bad credentials" and "repository not authorized" errors
- Disconnecting and reconnecting the repo from Settings did not resolve it
- Duplicating the service results in a generic "There was an error deploying from source" error
1 Replies
Status changed to Awaiting Railway Response Railway • 24 days ago
23 days ago
This is a known issue where the auto-deploy trigger binding becomes stale after revoking and re-authorizing the GitHub App. Deployments appear stuck at the snapshot step because the underlying "repository not authorized" error gets masked by retry logic.
We recently shipped a fix that lets you manage this directly. In your service settings, you should now see whether auto-deploys are configured and if there's a permission issue preventing them from working. You can re-enable auto-deploys from there without needing to reconnect the repo.
If that doesn't resolve it, go to GitHub Settings > Applications > Railway App > Configure and confirm the Railway App has access to your repository. Then go to your Railway account settings, unlink and relink the GitHub integration, and reconnect the repo from the service settings.
Status changed to Awaiting User Response Railway • 23 days ago
16 days 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 • 16 days ago