a month ago
We've been pushing multiple commits to main in our sales-report service, and Railway consistently shows "Deployment successful" / "Active" for each one. However, the code actually running in the container does not match the latest source.
Concrete evidence:
Latest deployment (Deployment ID: 96b667d9-dfaa-4517-8f80-760984420b47)
The container's dist/index.js was built at: 2026-07-21T21:56:59Z
At that point, server/routers.ts on GitHub main already contained a console.log('[deleteMovement][DEBUG]', ...) statement inside the deleteMovement function
That log line is completely absent from the deployed dist/index.js
In other words, the build step (pnpm build) is not picking up the latest source — it appears to be reusing a stale build artifact
Steps already tried (none worked):
Multiple fresh commits and pushes to main
Manual service Restart
Manual Redeploy from the dashboard (still shows the same stale behavior after redeploying — confirmed via the same debug-log test, deployment bd21be0e)
What we're asking:
Please perform a clean rebuild with the build cache fully invalidated for this service, and if possible let us know why the cache didn't detect the source changes.
Project: 정산웹앱 (formerly exquisite-gentleness)
Service: sales-report
Domain: mywhiskytable.up.railway.app
Pinned Solution
a month ago
Try disable the build cache, add NO_CACHE=1 to your environment variables
You can also try Deploy Latest Commit by Opening the service > Open command palette (Ctrl+K) > select Deploy Latest Commit
5 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Try disable the build cache, add NO_CACHE=1 to your environment variables
You can also try Deploy Latest Commit by Opening the service > Open command palette (Ctrl+K) > select Deploy Latest Commit
Status changed to Solved 0x5b62656e5d • about 1 month ago
a month ago
Additional symptom: The frontend static assets are now out of sync with the deployed HTML as well. When requesting the JS bundle file referenced by the deployed index.html (e.g. index-XwZ4EL_C.js), the server returns an HTML page instead of the actual JavaScript. As a result, the app's settlement (정산) page fails to load at all — confirmed across multiple different staff members' devices simultaneously, so this is not a per-device browser cache issue.
We tested the backend API directly (settlement.getMonthlySummary) and it responds with HTTP 200 normally across all branches, so this appears to be purely a static asset / build artifact mismatch, not a backend issue.
We also tried forcing a fresh deploy with an empty commit afterward, which did not resolve it.
This is now blocking our staff from accessing settlement data entirely, so it's fairly urgent on our end. Any update would be appreciated.
Status changed to Awaiting Conductor Response Railway • about 1 month ago
Status changed to Awaiting User Response Railway • about 1 month ago
jhyun860-source
Additional symptom: The frontend static assets are now out of sync with the deployed HTML as well. When requesting the JS bundle file referenced by the deployed index.html (e.g. index-XwZ4EL_C.js), the server returns an HTML page instead of the actual JavaScript. As a result, the app's settlement (정산) page fails to load at all — confirmed across multiple different staff members' devices simultaneously, so this is not a per-device browser cache issue. We tested the backend API directly (settlement.getMonthlySummary) and it responds with HTTP 200 normally across all branches, so this appears to be purely a static asset / build artifact mismatch, not a backend issue. We also tried forcing a fresh deploy with an empty commit afterward, which did not resolve it. This is now blocking our staff from accessing settlement data entirely, so it's fairly urgent on our end. Any update would be appreciated.
a month ago
"Update: We created a brand-new second service in the same project, pointing to the same repo/branch, with a fresh domain. The exact same symptom (JS returns HTML) appeared on this brand-new service too. This rules out a stale container on our end — the issue must be at the account/workspace-level edge or routing layer, not specific to any one service."
Status changed to Awaiting Conductor Response Railway • about 1 month ago
a month ago
If it's a new service, it should deploy a fresh build, does your local project work as expected? If so, can you verify that the latest commit deployed on railway match the latest commit on your local branch?
Status changed to Awaiting User Response Railway • about 1 month ago
23 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 23 days ago