Netlify Environment variable resolving to undefined on some deployments

Support
1

We have an application with multiple tenants deployed via Netlify. In the last few weeks many of the tenants are failing certain tasks because the key we deploy as environment variable resolved to undefined. I have checked all of the problematic deploys and the env variable is set according to the UI, but adding logging code shows that variable as undefined when running in a Netlify function.

This code has not changed in many months, and was working fine. I do not believe it would be even possible to invalidate an environment variable via code, but I have scanned the repository and this env var is accessed only once. All other variables appear to be resolving correctly.

This is an Astro site using Astro js version 2.10, with the @astrojs/netlify adapter versioned as ^2.6.0.

Some example site IDs where we are seeing this issue:

65ed38ba-bdca-4b23-8441-c09367d23772

a2e7f390-2a7f-493b-8c4f-c4562221c2b6

40990203-bca3-44e6-8ec5-6632142b2dc7

The code accesses the variable as follows:

const IIIF_KEY = import.meta.env.IIIF_KEY;

export const post: APIRoute = async ({ request, cookies }) => {
  // Verify if the user is logged in
--<snip>--

Logging added to the problematic sites show IIIF_KEY as undefined. Yet the value in the UI is valid.

2

Is there a way to reproduce the issue for us?

3

Well I could show you the logs where it is failing. As I said, it should work and has for awhile.

5

Hey Lorin,

Thanks for submitting a support ticket and apologies again for the hassle. We’ve followed up there!

6

Has there been any update on this? I think I’m seeing it too in one of my deployments, it was working fine until we did a deployment last week and it wasn’t able to access the environment variable like it did before.

We’re not using the Netlify adapter for this and just doing a static build, if that helps narrow it down.

7

Are you using github secrets by any chance?

8

I am not but I have figured it out so apologies for troubling you!

For anyone else that might end up here with a similar problem, if you’re using Turborepo then it might be this, v2 must have changed how this worked and our environment variables weren’t configured in the turbo.json correctly and it had nothing to do with Netlify (the env var is only used on the deployed version!).

9

No worries! thanks for writing back in and sharing your solution with the community.

1 Like