Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.

This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

• Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
• Keep it private and close the thread - Nothing becomes public. The thread closes, since this isn't something Railway support can take further.

Hey, I appreciate that. But I'm going to push back a little bit because this is new. This has never happened with Railway before. This has started happening over the last seven business days.

I'm not sure what configuration would change in our app to not allow it to build. Also there's some conflicting data because when we push it to production or sorry when we push to staging which is also on railway it deploys and cuts over within 30 seconds zero issues same configuration. But for some reason this instance continues to have issues.

So when I have my staging environment which is matched to production and it rolls over cuts over goes live very fast on the same GitHub code pushes but then for some reason my production instance doesn't I feel like there's a mismatch there and I'm not sure what configuration would be different between the two that would cause this. Anyways thanks for the help I just wanted to flag this cuz I don't know what to do with our railway settings.

This still looks like an application-level problem, so Railway support can't take it further, but the community can. The buttons below are still live: open the thread up as a public bounty after editing out anything sensitive, or keep it private and close it.

Hey community, Railway wants to gaslight me into this being an application problem. Even though I have two matching instances on Railway, one deploys and cuts over within 30 seconds or less, the other one doesn't cut over ever. But yet it's somehow my fault.