17 days ago
Newly-added service variables are saved in my dashboard but are NOT being injected into the container's runtime environment. I logged os.environ.keys() at startup — the newly-added variable is completely absent from the container, while variables added before the May 19 outage work fine. My env var count is stuck at exactly 60 across every redeploy, even though the dashboard shows 7 service variables.
Already tried (none worked): deleting/re-adding via Raw Editor, adding a differently-named test variable (also failed to propagate), detaching and reattaching the GitHub repo, and multiple redeploys.
This looks like a post-outage deployment-state issue. Could a Railway team member reset/refresh the deployment pipeline state for my service?
Project ID: bf3b11e2-4249-47a0-bc16-c494eb4a7e5c
Service ID: deadbe07-94a4-4181-893f-d3f5cf982a00
Service: BiznessKid (production)
2 Replies
Status changed to Awaiting Railway Response Railway • 17 days ago
16 days ago
When you add or change variables, they appear as staged changes and must be deployed using the "Deploy" button in the staged-changes banner on the canvas. Just wondering if it was semantics but want to make sure we didn't miss this - a "Redeploy" from the deployment menu would just recreate the deployment with the exact same configuration as the original and not pick up staged changes. If you haven't already, could you head back to the canvas, look for the purple staged-changes banner, click "Details", then "Deploy" to apply your new variables? If that's what you've been doing please let us know and we'll dig into why this isn't working for you
Status changed to Awaiting User Response Railway • 16 days ago
chandrika
When you add or change variables, they appear as [staged changes](https://docs.railway.com/deployments/staged-changes) and must be deployed using the "Deploy" button in the staged-changes banner on the canvas. Just wondering if it was semantics but want to make sure we didn't miss this - a "Redeploy" from the deployment menu would just recreate the deployment with the exact same configuration as the original and not pick up staged changes. If you haven't already, could you head back to the canvas, look for the purple staged-changes banner, click "Details", then "Deploy" to apply your new variables? If that's what you've been doing please let us know and we'll dig into why this isn't working for you
16 days ago
That fixed it — I'd been using Redeploy from the deployment menu instead of deploying staged changes from the canvas banner. The variable is now in the container. Thank you
Status changed to Awaiting Railway Response Railway • 16 days ago
Status changed to Solved Railway • 16 days ago