I’m not paying for that answer

Try disable the Build Cache by add NO_CACHE=1 to your Service Variables

You're not paying, Railway is paying someone else on your behalf to answer. No money is spent on your account, Railway covers that

I’m sorry for my comment it premature and silly. The fix did not work. my production is still showing stale package from a week or two ago. The cache isn’t clearing or something

Can u manually clear the repo cache for my project

The NO_CACHE=1 variable broke the build entirely — deployment failed with "failed to solve: secret NO_CACHE not found." I removed it and the service redeployed, but it's still serving the stale bundle.

What I tried and when (all times CDT, Oct 5):

• ~1:00 PM: Redeployed existing frontend service multiple times — each reported "successful" but served byte-identical bundle main.4c7881c6.js with zero references to OutreachDraftCard (component added to frontend/src/components/ Sept 27, present in current main)

• ~1:30 PM: Disconnected and reconnected GitHub repo on the service — no change. Verified service config is correct: repo ryanmena504-gif/GEAUXleads, branch main, root directory /frontend, auto-deploy on. GitHub App has "All repositories" access.

• ~1:45 PM: Pushed trivial README commit to trigger fresh build — deployed "successfully," bundle unchanged

• ~2:10 PM: Deleted the frontend service entirely and recreated it from scratch — new service still builds the identical stale bundle

• ~2:20 PM: Set explicit build command (npm run build) and start command (npx serve -s build -l 8080) on new service — production build now runs correctly, but from stale source

• ~2:50 PM: Added NO_CACHE=1 per your suggestion — build failed immediately with "failed to solve: secret NO_CACHE not found." Removed it.

Current state: New service at geauxleads-production-15c7.up.railway.app is online and building correctly, but Railway is compiling source from before Sept 27. The repository cache on your end appears frozen — new services, fresh GitHub reconnects, and new commits all produce the same stale output.

What I need: Can you manually clear the repository/source cache for this project on your end? Nothing I can do from the dashboard invalidates it.



The NO_CACHE=1 variable broke the build entirely — deployment failed with "failed to solve: secret NO_CACHE not found." I removed it and the service redeployed, but it's still serving the stale bundle.

What I tried and when (all times CDT, Oct 5):

• ~1:00 PM: Redeployed existing frontend service multiple times — each reported "successful" but served byte-identical bundle main.4c7881c6.js with zero references to OutreachDraftCard (component added to frontend/src/components/ Sept 27, present in current main)

• ~1:30 PM: Disconnected and reconnected GitHub repo on the service — no change. Verified service config is correct: repo ryanmena504-gif/GEAUXleads, branch main, root directory /frontend, auto-deploy on. GitHub App has "All repositories" access.

• ~1:45 PM: Pushed trivial README commit to trigger fresh build — deployed "successfully," bundle unchanged

• ~2:10 PM: Deleted the frontend service entirely and recreated it from scratch — new service still builds the identical stale bundle

• ~2:20 PM: Set explicit build command (npm run build) and start command (npx serve -s build -l 8080) on new service — production build now runs correctly, but from stale source

• ~2:50 PM: Added NO_CACHE=1 per your suggestion — build failed immediately with "failed to solve: secret NO_CACHE not found." Removed it.

Current state: New service at geauxleads-production-15c7.up.railway.app is online and building correctly, but Railway is compiling source from before Sept 27. The repository cache on your end appears frozen — new services, fresh GitHub reconnects, and new commits all produce the same stale output.

What I need: Can you manually clear the repository/source cache for this project on your end? Nothing I can do from the dashboard invalidates it.



Pushed trivial README commit to trigger fresh build — deployed "successfully," bundle unchanged

The bundle wouldn't change from just a changed README commit

Redeployed existing frontend service multiple times — each reported "successful" but served byte-identical bundle main.4c7881c6.js with zero references to OutreachDraftCard

Redeploying doesn't pull new changes, it redeploys that existing change

I investigated a little and checked your deploys from your GitHub repo, interestingly I can see you keep deploying 2 week old commits. More recently you did deploy a recent commit but the build failed (or was aborted). Can you verify a few things:

• Do you have watch paths set on Railway?
• Do you have the branch overridden on Railway?
• Have you tried, from your Service, doing ctrl+k -> Deploy latest commit on Railway?