Check if you're adding variables in the correct environment (production, staging etc.). You can try setting NO_CACHE=1 in your variables, to rule out a caching issue. And also, are you using a Dockerfile?

I haven’t seen this personally, but I dug up a couple of likely causes:

• Platform race / state inconsistency, can leave staged vars visible and not applied. See: dev.to article.
• Wrong scope / staged changes not deployed, make sure your vars are service‑scoped and you hit Update / Deploy. See: Railway docs on Variables.

Add this to the top of your app to verify at runtime:

console.log('ENV_KEYS', Object.keys(process.env).length);
console.log('RAILWAY_TEST_VAR', process.env.RAILWAY_TEST_VAR);

If it still fails after confirming scope and redeploying, collect build/runtime logs and ask staff to perform a state reset.

something is just stuck on Railway's end that you have no way to fix yourself. You already found the right thread with Ray, just go back there, reference it, drop your project UUID and tell them whats happening. They'll know what to do.

Update: still happening after Raw Editor wipe+paste + auto-deploy.

Test: railway variable set RAILWAY_BUG_TEST=hello → process.env null after restart.

Project: profound-love (24aee7a7-b0f2-4832-af35-c55c02f8c047)

Service: Gruntownie.eu (7a189b8e-b74d-413e-b11e-534544be36cd)

Please do state reset like Ray Chen did for thread b710fab5

(https://station.railway.com/questions/infinite-applying-changes-b710fab5).

PLUS: właśnie zrobiłem 4 testy:

1. Service Vars CLI → null

2. Service Vars UI Raw Editor → null

3. Shared Vars UI z reference do service Gruntownie.eu → null

4. Volume file → empty po deploy

WSZYSTKIE 4 metody fail. Tylko 3 vars z marca propagują.

To oczywisty stale state w project. PROSZĘ ESKALUJ DO STAFF.

@brody @echohack @raychen