Hey there! We've found the following might help you get unblocked faster:

• 🧵 Ignoring latest commit

• 🧵 Deployment doesn't match latest commit

• 🧵 Deploying Latest Commit

If you find the answer from one of these, please let us know by solving the thread!

This is happening for me - definitely a bug or completely overlooked. I can switch to a different branch and the purple deploy will be prominent - go back to main and it disappears.

If I re-deploy from the deployments - its clearly showing the commit sha from a previous commit. It's not picking up latest main and there is no "new" deployment that will check latest.

Kind of stuck.

Issue Summary: Persistent content caching despite successful deployments. GitHub repository contains updated content, but Railway serves outdated versions even after multiple troubleshooting attempts.

Evidence of the Problem:

• GitHub repository shows current content (commit 63d51da)

• Railway builds successfully from identical commit

• Multiple platforms (Vercel, Render) pull same git commit, confirming repository state

• Cant access updated dashboard showing old dashboard

• cant access admin dashboard after changes made in development

• Updated scoring methodology page displays old content on Railway deployment

• Fresh Railway deployments still serve cached content

Troubleshooting Steps Attempted:

1. Multiple fresh deployments - Deleted and recreated services completely

2. GitHub integration - Connected directly to repository instead of CLI uploads

3. Build cache disabling - Added NO_CACHE=1 environment variable

4. Browser cache elimination - Tested in incognito, hard refresh, multiple browsers

5. Repository verification - Confirmed all platforms pull identical git commit (63d51da)

6. Build process validation - Railway logs show successful builds and health checks

Current Status:

• Railway builds complete successfully

• Health checks pass

• Server functionality works correctly

• Static assets serve outdated content despite fresh builds

• Issue persists across completely new Railway projects

Business Impact: Cannot demonstrate current application version to investors or integrate with external services (Zapier) due to outdated interface and documentation being served instead of current GitHub content.

The evidence strongly suggests Railway's CDN or asset serving infrastructure has persistent caching behavior that survives fresh deployments and build cache disabling.

Just now I updated my gitignore to remove /docs and I am still seeing outdated content. I need help on this asap.

Thank you.

I have same issue, I keep trying new pushes to production can't see the particular changes I made. I successfully pushed to dev on Tuesday, production is still stuck on old commit. What's weird, if I add startup logs, I can see them..

I am having the same issue (a5f1e7a5-0cad-4dc4-853a-d531320892eb). Has anyone found a solution or is there a moderator/admin from Railway that can respond?

Solution: Remove build artifacts (dist/build folders) from git tracking

I had the same issue: Railway showed the latest commit, but the deployed site was serving old content. The fix was removing the dist folder from git tracking.

The Problem:

If you commit your dist or build folder to git, Railway may:

• Use stale build artifacts instead of rebuilding

• Serve outdated files that reference old asset hashes

• Skip or conflict with the build process

• Cause containers to stop due to mismatched files

The Solution:

1. Add build folders to .gitignore (if not already):

      dist/

      build/

      *.log

2. Remove dist from git tracking (keeps files locally):

      git rm -r --cached dist

      git commit -m "Remove dist folder from git tracking - should be built, not committed"

      git push

3. Ensure Railway always builds fresh - Update your nixpacks.toml or build script to clean before building:

      [phases.build]

      cmds = ["rm -rf dist || true", "npm run build"]

4. Add proper cache headers to your server (if serving static files):

• HTML files: no-cache, no-store, must-revalidate

• Hashed assets (JS/CSS): max-age=31536000, immutable

Why This Works:

Build artifacts should be generated during deployment, not committed. When Railway sees dist in git, it may use those files instead of running a fresh build, leading to stale content.

After removing dist from git, Railway will:

• Always build fresh files

• Use the correct asset hashes

• Serve up-to-date content

This resolved my deployment issues. Hope this helps others facing the same problem.