19 days ago
Environment variables configured in the service Variables panel are not being injected into the container runtime.
Project: joyful-energy
Service: web (Service ID: a70b27eb-f348-4972-b7c2-b2cf4085b523)
Environment: production (Environment ID: 8147d6f2-19e4-4953-b862-cad37616d1b2)
Deployment ID: b3457df9-869d-41cf-8a0b-269ef1090823
Steps already taken to diagnose:
- Confirmed 10 variables exist in the Variables panel (ANTHROPIC_API_KEY, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REDIRECT_URI, GOOGLE_REFRESH_TOKEN, NODE_ENV, PACHO_EMAIL, ZOOM_ACCOUNT_ID, ZOOM_CLIENT_ID, ZOOM_CLIENT_SECRET).
- Created a brand-new test variable (TEST_VAR=hola123), deployed, and confirmed via Console that
echo $TEST_VARreturns nothing. - Ran
envin the Console — output only shows Railway-injected variables (RAILWAY_*, PORT, NODE_ENV, PATH, etc.) and none of the custom variables set in the panel. - Tried: Restart, full Redeploy, and disconnecting/reconnecting the GitHub repo (pacho-santos/pacho-os, branch main). Problem persists identically after each attempt.
- Verified there's no committed .env file in the repo, no custom Dockerfile, and the build command is default (Railpack/Nixpacks).
Only NODE_ENV (which appears to be set automatically) and Railway's own RAILWAY_* variables are present in the running container. No manually-set variable — old or newly created — is reaching the process.
This is blocking our app's Google Calendar and Gmail integration in production. Any guidance on what could cause this desync between the Variables panel and the actual container environment would be greatly appreciated.
Update: I found an identical case in the community forum — "Environment variables not available inside container after deploy" (thread by kalkener, posted 1 day ago). Railway support (angelo-railway) confirmed it as "a known stuck state" where staged variable changes are not being committed to the environment despite clicking Deploy, and stated they were resolving it from their side.
This matches my situation exactly: variables show correctly in the panel, deploys complete successfully, but the container only receives Railway's own auto-injected variables — none of the manually-set ones, old or newly created, ever reach the runtime.
Could you please check if my service (web, Service ID: a70b27eb-f348-4972-b7c2-b2cf4085b523) is in the same stuck state, and apply the same fix?
1 Replies
Status changed to Awaiting Railway Response Railway • 19 days ago
19 days ago
We've confirmed this is on our side, not your configuration. Your variable changes are staged but a known stuck state is preventing them from committing into the environment, which is why nothing reaches your container. We're getting it cleared and will follow up here once your variables apply, after which a redeploy will pick them up.
Status changed to Awaiting User Response Railway • 19 days ago
12 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 • 12 days ago