Environment variables marked as Sensitive cause authentication failures for my application at runtime. When the same variable is created without the Sensitive flag (identical value), it works correctly. Confirmed across two different services: a Supabase Postgres connection string (Prisma P1000 auth…

Hi @anshumanb , Thanks for the response. After recreating the issue multiple times last night, I tried it again this morning and it seems to be working now.

Hi @scottjwood , I couldn’t recreate the issue as of now. Here are the steps I tried: Created a new project and added both secret/non-secret vars. Both were readable at runtime. Edited the variables later on, new values were readable after a redeploy (as expected). Edited the variables again, this …

We’re seeing this same exact issue. For the production environment it works correctly and it loads the sensitive environment variables, but for our preview and custom staging environment it doesn’t load them properly. Only once we change that they are not sensitive are they loaded correctly during …

Hi @miljantekic , could you confirm if this is still an issue?

Environment variables marked as Sensitive cause authentication failures

Help

anshumanb (Anshuman Bhardwaj) April 20, 2026, 5:45am 2

Hi @scottjwood, welcome to the Vercel Community!

Thanks for reporting it. Let me share with our team.

Topic		Replies	Views
Cannot set Integration Environment Variables to Sensitive Help feature-request	1	59	April 20, 2026
Sensitive ENV VAR does not get loaded locally with vercel dev, even if added to local env file Help vite	3	250	November 21, 2024
Wrong ENV Var Value in Production After Redeploy Without Cache Help	15	162	November 4, 2025
Bug 🐛 sensitive environment variables Feedback	3	72	January 7, 2026
🐞 Bug Report: Stale Environment Variables in vercel dev Discussions	0	57	September 25, 2025

Environment variables marked as Sensitive cause authentication failures

Related topics