2 months ago
I currently have Railway PR deployment set up for my repo. And i also have some post deploy ci workflow running on it. It was working completely fine just 2 days ago but now it hasn't triggered the workflow no matter how many times i push or commit.
I've tried:
- Disconnecting and reconnecting github repo
- Checked the railway permissions: has read and write: ``` Read access to metadata Read and write access to actions, administration, checks, code, commit statuses, deployments, pull requests, and workflows ```
- Tried turning on wait for ci and turning it off again but no change
I've been looking at the deployment logs and the railwayapp-bot hasnt triggered a deployment even though i pushed multiple commits.
https://github.com/kzoeps/ePDS/deployments
https://github.com/Kzoeps/ePDS/pull/11 this is the pr where im trying to trigger my workflow.
Weirdly up until commit feab5d0a029c4bf538967dd7512c996427d2014f it was running perfectly. but that was 2 days ago and ever since yesterday its not been triggering any autodeploys
7 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
I have had this exact same issue. The deployments began showing up as "Checks", and now push to main (which does deploy) doesnt show up as a Deployment either. I have since tried to reconnect github/Railway and now cant deploy at all ☹
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
nice it worked but what was the issue for this? and how do i know in the future that it might be a railway issue and not my issue. Sorry i spend a whole day debugging this to no avail and if id known sooner that it was a railway issue i would've left it
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Echoing this question - https://status.railway.com/ doesn't show any obvious extended outage for deployments in the last couple of days.
2 months ago
The status wasn't propagating; this had zero effect on any workloads. Little bugs like this are not called as incidents.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
so next time if everything is configured right and mostly follow the steps i did above and i still dont see it in the list of deployments in the github then i just file a ticket for it?
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Yes, if you've verified your GitHub permissions and tried reconnecting the repo with no change, filing a ticket here is the right next step. We can check on our end whether the deployment triggers are set up correctly for your service.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Solved kzoeps • about 2 months ago