Potential bug with env variable settings page?

Feedback
1

Hi all,

I think there is possibly a bug with applying Env’s on the project/settings/environment-variables page, but maybe I am being dumb.

In the past I was able to add Env’s directly on the environment-variables settings page (i.e. project/settings/environment-variables) and you could select what environments to add them for via a tickbox (say production, development, etc).

I noticed recently new environment variables are not actually being added to any environments, despite the UI on Vercel indicating they were in place (and they are persisted on this page after logging out and back in, navigating off the page etc), but they are not actually present in the Env when you go and deploy.

What I know

  • Deploying via the CLI (i.e. running vercel) and it would work with my local env applied and deployments succeed as expected.

  • I was also able to validate that the Env’s added via the UI are not actually applied using vercel UI (i.e. running vercel env ls would NOT show env variables added via UI on project/settings/environment-variables ).

  • Adding Env’s via the environments page works, for example project/settings/environments/environment-name (example: project/settings/environments/development). Env’s added here work as expected and can be seen with vercel env ls.

Maybe I am missing something here, but it seems like a bug, or at least the UI is misrepresenting the Env data. For me there is no blocking issue with my deployments as there is multiple workarounds that work fine, but would be good if someone could take a look as I am sure there are others who are confused also.

Cheers.