are you referencing these variables in your build step?

Not in the build step specifically, no. These variables are used in the applications hosted on the services themselves. I've even gone so far as to delete the environment variables entirely, and redeploy the services. The build logs are still showing the same errors, referencing env variables that no longer exist.

I think its build cache issue..Did you try to redeploy ? Try adding NO_CACHE=1 as a service variable and redeploy. That disables build layer caching.

https://docs.railway.com/builds/build-configuration#disable-build-layer-caching

Same deal on both services even with no cache

install mise packages: node

25ms

ERROR: failed to build: failed to solve: secret SESSION_GRACE_EXIT_TIMEOUT_SECONDS: not found

Removed the env variables from the codebase entirely too, still no dice

For some reason your build plan is trying to load those values as “build secrets”, but Railpack can’t find variables with those exact names available to that environment..

Yeah super strange. I wonder if something misconfigured when I cloned our staging environment when we launched? Kind of at a loss here

Can you also check your railpack.json for a "secrets" field? It should be empty or not present if you've removed everything. Also do a quick search across your repo

No secrets field in the railpack.json in any of my 3 services, no references across the entire codebase for those .env variables either

can you also check in railpack-plan.json if it exists ? also you redeployed right?

No railpack-plan exists. And yep yep! Redeployed both services with the same result.

can you share build logs before error?

Absolutely, see attached!

Did you seal any variables in staging before cloning to production? sealed variables don't copy over when duplicating environments ..

None at all - for what it's worth we have many other env variables, all behaving properly.

I Have not yet tried to share them with other services (they're all shared appropriately as it stands, and the app is working), but don't want to try in case it breaks as well.

so other variables are working fine..how are those variables shared with the services ?. are you using reference variables like ${{shared.SESSION_GRACE_EXIT_TIMEOUT_SECONDS}} on each service?

ohhh my goodness....they were somehow still stuck in the services themselves? Removed them manually from there as well and the deploy went through. Testing a couple more things but I think we're good here.

Ah nice, glad you found it...those leftover variables were tripping up the build!!!

What the solution? I'm having similar issue, regenerating package-lock has no effect