2 months ago
Our GitHub auto-deploy webhook is working correctly — pushes to main trigger builds and deploy successfully on Railway. However, Railway is not sending deployment status callbacks to GitHub.
Our repo's Deployments section (github.com/claudebot001/flipster-dispo-suite → Deployments) has been stuck at 228 since yesterday morning. We've had 15+ successful deploys since then, all triggered via the GitHub webhook, but none are reflected on GitHub.
Project: splendid-reflection
Service: flipster-dispo-suite
Environment: production
Repo: claudebot001/flipster-dispo-suite
Inbound (GitHub → Railway build trigger) working
Outbound (Railway → GitHub deployment status API) not firing
Attachments
4 Replies
2 months ago
We can confirm your service is linked to the repo and deploying successfully. GitHub deployment status callbacks are a platform-side integration, and we are aware this can sometimes stop functioning while inbound triggers continue to work. Try disconnecting the GitHub repo from your service settings and reconnecting it, which refreshes the integration tokens. Also verify that the Railway GitHub App installation at https://github.com/settings/installations has the latest permissions accepted, as outdated permissions can prevent us from writing deployment statuses back to GitHub.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
I have had the same issue with Deployments not showing up in github, in PR and production env.
Disconnecting/reconnecting github has completely broken and now Railway cannot see my repo at all. Please help.
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
Yes sir! Back in business. Thank you.
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved claudebot001 • about 2 months ago