We've looked into this from our side and haven't found anything on the Railway platform that explains what you're seeing, so working it out means digging into your specific setup.

That's exactly what 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 and the thread closes.

Can you share your build repo, so that a possible replication can be created? It's possible that one of the builders had caching from previous iteration and thus appeared faster.

There are several steps you can take to ensure faster builds, based on previous container image layers

actually its a client project, so i'm not allowed to share it, but if we talk about cache i have built 5-6 build and i think that sufficient to cache the build and its still taking same time for new builds