Deployments appear to be stuck

thewiseoldsageltd
FREE

2 months ago

  • Deployment caching issue - new builds not being served

  • Still serving old bundleindex-DVRecB4k.js instead of new index-DSOJeELu.js

  • Multiple redeploy attempts failed including "clear build cache" option

  • New files created but not detected by deployment system

$10 Bounty

6 Replies

Railway
BOT

2 months ago

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

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

thewiseoldsageltd
FREE

2 months ago

Sorry doesn't resolve - thanks

Status changed to Solved brody • about 2 months ago

thewiseoldsageltd
FREE

2 months ago

Hello - this isn't resolved

Status changed to Awaiting Railway Response Railway • about 2 months ago

brody
EMPLOYEE

2 months ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open brody • about 2 months ago

thewiseoldsageltd
FREE

2 months ago

Thanks Brody, not sure if this helps but this is the solution I've been told needs to happen:

Frontend Bundle Caching(Railway Support)

  • Current: Railway serving old index-DVRecB4k.js (crashes)

  • Should serve: New index-DSOJeELu.js (works perfectly)

  • Solution: Railway support to clear frontend bundle cache

thewiseoldsageltd
FREE

2 months ago

I believe it's the same CDN caching issue as in this post https://station.railway.com/questions/urgent-deployments-successful-but-railw-8358a6a5

clashing
HOBBY

2 months ago

thewiseoldsageltd, you can check out my solution to a similar query! It tells you the steps that you can take to remove the caching thing!

https://station.railway.com/questions/forcing-fresh-docker-builds-on-railway-bfd0872c#0yv9

This works if you are using a server thing/Docker image to build the application.

In case you are using a GitHub repo, apart from setting the NO_CACHE to 1 (as told in the linked post), you can do this to make sure that the latest commit is being fetched to make the build:

Select the Railway-service which you want to update! Press Ctrl/Cmd + K and then type Deploy Latest Commit, & select it. That would deploy the fresh instance of your GitHub repo code.

Do let me know if that helps or not. If it helps, then do mark this as the solution

Deployments appear to be stuck - Railway Help Station