2 months ago
My Railway service variables appear correctly in the Variables UI, but none are injected into the running Node.js service.
Service: policy-advisor-hub
Environment: production
Evidence from the Railway Console after using the Variables Raw Editor, clicking Update Variables, and manually redeploying:
ALLOWED_EMAILS=0
AUTH_BASE_URL=0
RESEND_API_KEY=0
JWT_SECRET=0
The application reads process.env at runtime and sees all four variables as empty. The same behavior persists in a new container after redeploy.
Could Railway please investigate and reset the service/environment variable state? I can provide non-sensitive deployment IDs or logs if needed.
1 Replies
2 months ago
The four variables (ALLOWED_EMAILS, AUTH_BASE_URL, RESEND_API_KEY, JWT_SECRET) are currently staged but not yet applied to the production environment. Staged variable edits are not injected into deployments until you click Deploy on the changes bar at the top of the project canvas, and a manual redeploy from the service page does not apply them. Click Deploy on that bar and the next deployment will pick up all four variables. You can reply here once you have applied them if you would like us to verify the state.
Status changed to Awaiting User Response Railway • about 2 months ago
a month 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 • about 1 month ago