15 days ago
I can see the push went through, it landed on Github, but there's no building activity on Railway.
Is this an issue on the Github side or Railway side?
2 Replies
15 days ago
Your services in the TreadCommand project are actually receiving GitHub push events, but several of them (dashboard, marketing-site, storefront) have their latest deployments in a SKIPPED state, and api-server-paid shows as REMOVED. The SKIPPED status means builds were triggered but intentionally not run, which typically happens when "Wait for CI" is enabled and a GitHub Actions workflow fails, or when watch paths are configured and the pushed files don't match. Please check your service settings for whether "Wait for CI" is toggled on (and verify your GitHub Actions are passing), and review any configured watch paths. You can also click "Show Skipped" in your deployment history to see the skipped deployments and their reasons.
Status changed to Awaiting User Response Railway • 15 days ago
15 days ago
i simply created a "force_build.txt" on my backend that deploys to "api-server-paid" and it worked this time. i made no other changes to my code or railway setup . im still confused on why i hiccupped, but the issue is resolved now.
Status changed to Awaiting Railway Response Railway • 15 days ago
Status changed to Solved curiouskal • 15 days ago