Hello,

I have confirmed that your variables are being passed to the build, so the issue would lay elsewhere within your configuration.

I have gone ahead and bountied this thread so that the community can help you!

Please share the relevant logs so that other community members can have a good chance at helping.

Best,
Brody

Okay, perhaps I am just not familiar enough with the UI to understand it.

Can someone let me know why my Deployment Details reports "0 Variables"?
I have attached a screenshot of the view in question.

And here is a screenshot of my configured variables within the service.

Purely just a UI bug.

The error I am receiving is a 401 error when pulling a private package from GitHub. I have validated that the token I am passing in is valid and works in other test environments. Also, this service worked with this exact configuration before the outage.

Perhaps your token has expired, either way, I will let the community involve themselves as this is not a platform issue.

Though I have ticketed the UI bug.

Again, the token has not expired and is functioning as expected from other environments.

Your variables are being passed to the build, I have verified that fact.

After further inspection, I was able to confirm — just like @Brody said — that the environment variables were being passed to the build.

What I still don’t know for sure is why the token stopped working from within Railway. It was valid, not expired, and worked fine locally. But after regenerating it, the service started working again.

My best guess? GitHub may have rate-limited or temporarily blocked access using that token from Railway, possibly because my deploys were retrying every 5 minutes during the outage.

¯\_(ツ)_/¯