a month ago
I encountered an issue where a newly created sealed environment variable appeared in Railway’s configuration but was unavailable to the build. Re-entering its value resolved the issue while keeping the variable sealed.
What happened
- I created
EXAMPLE_API_KEYas a sealed variable from the start. - About 20 minutes later, a deployment failed because our build-time validation rejected that variable as undefined or empty.
- A redeployment with the build cache disabled also failed in the same way.
- I re-entered the variable’s value, keeping it sealed.
- The resulting deployment passed both build-time and startup environment validation.
All three deployments used the same application commit.
The variable update was the only configuration change between the last failed deployment and the successful one.
Environment
- SvelteKit with Vite
- Railpack / V3 build environment
- Failed builds used Railpack 0.41.0 and 0.42.0
- Node.js 24.16.0
- pnpm 10.34.3
Our build-time validation reads process.env and requires a non-empty string. Other required sealed variables passed validation during the failed builds; only EXAMPLE_API_KEY failed.
Railway’s API confirmed that the variable existed and was marked sealed before the failed deployments.
Since sealed values cannot be read back, I cannot determine whether the original value was stored empty or was not injected into the build.
7 Replies
a month ago
Sealed variables are passed into builds the same way as regular variables, so the build should have seen EXAMPLE_API_KEY like your other sealed variables. There is a known case where a variable that is sealed at the moment it is created can end up saved with an empty value, and re-entering the value afterwards stores it correctly, which is consistent with what you saw.
Because sealed values cannot be read back, we can't confirm from your account whether that is exactly what happened to this variable. Variables that were sealed after already having a value are not affected by this case.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Sealed variables are passed into builds the same way as regular variables, so the build should have seen `EXAMPLE_API_KEY` like your other sealed variables. There is a known case where a variable that is sealed at the moment it is created can end up saved with an empty value, and re-entering the value afterwards stores it correctly, which is consistent with what you saw. Because sealed values cannot be read back, we can't confirm from your account whether that is exactly what happened to this variable. Variables that were sealed after already having a value are not affected by this case.
a month ago
So? If it is a known case as you said,
you know the bug but you are not trying to fix it?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We can't give you a commitment or a timeline on product changes from this thread. Our earlier reply offered a possible explanation, but because sealed values can't be read back by you or by us, we can't confirm whether the original value was stored empty or wasn't passed to the build.
What we can confirm from your description is that after you re-entered the value, the next deployment on the same commit passed both build-time and startup validation, so EXAMPLE_API_KEY is now being supplied as expected.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
We can't give you a commitment or a timeline on product changes from this thread. Our earlier reply offered a possible explanation, but because sealed values can't be read back by you or by us, we can't confirm whether the original value was stored empty or wasn't passed to the build. What we can confirm from your description is that after you re-entered the value, the next deployment on the same commit passed both build-time and startup validation, so EXAMPLE_API_KEY is now being supplied as expected.
a month ago
I understand you can’t commit to a fix or timeline.
Could you confirm whether this has been logged as a bug report and escalated to a human support or engineering team?
Your first reply mentioned a “known case.” Is there an existing issue this report can be linked to?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
There is no public issue we can link this report to, and we can't confirm from this thread whether it has been filed or escalated anywhere.
"Known case" in our first reply went too far. What we can confirm about how the product behaves is narrower. Sealed variables are passed into builds the same way your other sealed variables were. A sealed variable keeps whatever value was saved when it was created, and if that value was empty, the build gets an empty value. Sealing a variable that already has a value keeps that value. Because sealed values can't be read back, we can't tell whether your first save of EXAMPLE_API_KEY stored an empty value.
If you want to avoid this in future, set the value first, check that the build picks it up, and then seal the variable. Re-entering the value, as you did, also works.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
There is no public issue we can link this report to, and we can't confirm from this thread whether it has been filed or escalated anywhere. "Known case" in our first reply went too far. What we can confirm about how the product behaves is narrower. Sealed variables are passed into builds the same way your other sealed variables were. A sealed variable keeps whatever value was saved when it was created, and if that value was empty, the build gets an empty value. Sealing a variable that already has a value keeps that value. Because sealed values can't be read back, we can't tell whether your first save of EXAMPLE_API_KEY stored an empty value. If you want to avoid this in future, set the value first, check that the build picks it up, and then seal the variable. Re-entering the value, as you did, also works.
a month ago
Tell this to human.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
From the details you gave, the variable that failed was the only one sealed at the moment it was created, and re-entering its value fixed the build on the same commit. Sealed values can't be read back by you or by us, so we can't confirm whether the first save stored an empty value.
Status changed to Awaiting User Response brody • about 1 month ago
24 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 • 24 days ago